OPP: Fix two refcount bugs
PATCH 1/1 OPP: Fix two refcount bugs
In drivers/opp/of.c, there are two refcount bugs:
(1) in _of_init_opp_table(), of_put_node() in the last line is not needed as the 'opp_np' is escaped out into 'opp_table->np' and ’opp_table' is an out parameter.
(2) in _opp_add_static_v2(), we need call of_node_get() for the new reference created when "new_opp->np = np;" as new_opp is escaped out. Here we should also take care of the of_node_put() when 'new_opp' is freed based on the function description: "The opp can be controlled ... and may be removed by dev_pm_opp_remove".
NOTE: _opp_add_static_v2() is called by _of_add_opp_table_v2() in a for_each_available_child_of_node() which will automatically increase and decrease the refcount. So we need an additional of_node_get() for the new reference created in _opp_add_static_v2().
--- drivers/opp/core.c | 1 + drivers/opp/of.c | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-)
drivers/opp/core.c +1 -0
@@ -1576,6 +1576,7 @@ static void _opp_kref_release(struct kref *kref)list_del (&opp->node);mutex_unlock (&opp_table->lock); +of_node_put (opp->np);/* * Notify the changes in the availability of the operable * frequency/voltage list.
drivers/opp/of.c +1 -2
@@ -242,7 +242,6 @@ void _of_init_opp_table(struct opp_table *opp_table, struct device *dev, opp_table->np = opp_np;_opp_table_alloc_required_tables (opp_table, dev, opp_np); -of_node_put (opp_np); }void _of_clear_opp_table (struct opp_table *opp_table)
@@ -902,7 +901,7 @@ static struct dev_pm_opp *_opp_add_static_v2(struct opp_table *opp_table, new_opp->turbo =of_property_read_bool (np,"turbo-mode" ); - new_opp->np = np; + new_opp->np =of_node_get (np); new_opp->dynamic = false; new_opp->available = true;
Signature · 1 line
2.25.1
Quoted 14 lines · Liang He
In
drivers/opp/of.c, there are two refcount bugs:
(1) in_of_init_opp_table(),of_put_node()in the last line is not needed as the 'opp_np' is escaped out into 'opp_table->np' and ’opp_table' is an out parameter.
(2) in_opp_add_static_v2(), we need callof_node_get()for the new reference created when "new_opp->np= np;" asnew_oppis escaped out. Here we should also take care of theof_node_put()when 'new_opp' is freed based on the function description: "The opp can be controlled ... and may be removed bydev_pm_opp_remove".
NOTE:_opp_add_static_v2()is called by_of_add_opp_table_v2()in afor_each_available_child_of_node()which will automatically increase and decrease the refcount. So we need an additionalof_node_get()for the new reference created in_opp_add_static_v2().
Quoted 2 lines
Fixes f06ed90e7051 ("OPP: Parse OPP table's DT properties from _of_init_opp_table()")Fixes 274659029c9d ("PM / OPP: Add support to parse "operating-points-v2" bindings")
The way I designed the OPP core then was to make sure that np is only used for pointer comparison and nothing else after it is freed by calling of_node_put(). So it isn't a bug.
But I do understand that it has become difficult to track now if np can get used later on for other stuff as well or not and it would be better to keep the reference up in such a case.
That is, you can drop the Fixes tag as I don't want these to get backported, but yes patches are welcome.
Please prepare two separate patches, one for opp_table->np and one for opp->np. It is fine to add multiple patches even for the opp->np case, if the reasoning is different.
Quoted 23 lines
Signed-off-by Liang He <[email protected]>--- drivers/opp/core.c | 1 + drivers/opp/of.c | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-)drivers/opp/core.c +1
-0@@ -1576,6 +1576,7 @@ static void _opp_kref_release(struct kref *kref)list_del (&opp->node);mutex_unlock (&opp_table->lock); +of_node_put (opp->np);/* * Notify the changes in the availability of the operable * frequency/voltage list. drivers/opp/of.c +0
-0
drivers/opp/of.c void _of_init_opp_table(struct opp_table *opp_table, struct device *dev, · line 245
Quoted 4 lines
drivers/opp/of.c +0
-1@@ -242,7 +242,6 @@ void _of_init_opp_table(struct opp_table *opp_table, struct device *dev, opp_table->np = opp_np;_opp_table_alloc_required_tables (opp_table, dev, opp_np); -of_node_put (opp_np);
Where does this get dropped now ?
Quoted 14 lines
drivers/opp/of.c +1
-1}void _of_clear_opp_table (struct opp_table *opp_table)@@ -902,7 +901,7 @@ static struct dev_pm_opp *_opp_add_static_v2(struct opp_table *opp_table, new_opp->turbo =of_property_read_bool (np,"turbo-mode" ); - new_opp->np = np; + new_opp->np =of_node_get (np); new_opp->dynamic = false; new_opp->available = true;Signature · 1 line
2.25.1
Signature · 1 line
viresh
Quoted 3 lines · Viresh Kumar
Please prepare two separate patches, one for
opp_table->npand one foropp->np. It is fine to add multiple patches even for theopp->npcase, if the reasoning is different.
Also, please rebase on linux-next/master, in case you haven't.
Signature · 1 line
viresh
Quoted 22 lines · Viresh Kumar
Quoted 14 lines · Liang He
In
drivers/opp/of.c, there are two refcount bugs:
(1) in_of_init_opp_table(),of_put_node()in the last line is not needed as the 'opp_np' is escaped out into 'opp_table->np' and ’opp_table' is an out parameter.
(2) in_opp_add_static_v2(), we need callof_node_get()for the new reference created when "new_opp->np= np;" asnew_oppis escaped out. Here we should also take care of theof_node_put()when 'new_opp' is freed based on the function description: "The opp can be controlled ... and may be removed bydev_pm_opp_remove".
NOTE:_opp_add_static_v2()is called by_of_add_opp_table_v2()in afor_each_available_child_of_node()which will automatically increase and decrease the refcount. So we need an additionalof_node_get()for the new reference created in_opp_add_static_v2().Quoted 2 lines
Fixes f06ed90e7051 ("OPP: Parse OPP table's DT properties from _of_init_opp_table()")Fixes 274659029c9d ("PM / OPP: Add support to parse "operating-points-v2" bindings")The way I designed the OPP core then was to make sure that np is only used for pointer comparison and nothing else after it is freed by calling
of_node_put(). So it isn't a bug.
Quoted 7 lines
But I do understand that it has become difficult to track now if np can get used later on for other stuff as well or not and it would be better to keep the reference up in such a case.
That is, you can drop the Fixes tag as I don't want these to get backported, but yes patches are welcome.
I will drop the fix tags in new patches.
Quoted 4 lines
Please prepare two separate patches, one for
opp_table->npand one foropp->np. It is fine to add multiple patches even for theopp->npcase, if the reasoning is different.
Thanks, Viresh,
But is it OK if the two patches change the same file at same time?
I wonder if this will trouble you to merge them later.
If it is OK, I will begin to prepare the two patches based on same file.
Quoted 25 lines
Quoted 25 lines
Signed-off-by Liang He <[email protected]>--- drivers/opp/core.c | 1 + drivers/opp/of.c | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-)drivers/opp/core.c +1
-0@@ -1576,6 +1576,7 @@ static void _opp_kref_release(struct kref *kref)list_del (&opp->node);mutex_unlock (&opp_table->lock); +of_node_put (opp->np);/* * Notify the changes in the availability of the operable * frequency/voltage list. drivers/opp/of.c +0
-0@@ -242,7 +242,6 @@ void _of_init_opp_table(struct opp_table *opp_table, struct device *dev, opp_table->np = opp_np;
Quoted 5 lines
drivers/opp/of.c void _of_init_opp_table(struct opp_table *opp_table, struct device *dev, · line 245
Quoted 2 lines
drivers/opp/of.c +0
-1_opp_table_alloc_required_tables (opp_table, dev, opp_np); -of_node_put (opp_np);Where does this get dropped now ?
After I read the code, I think it is better to drop opp_table->np in '_opp_table_kref_release' just like we do for the 'opp->np' in '_opp_kref_release'.
If it is not OK, please correct me.
Quoted 3 lines
[ ... ]
Also, please rebase on linux-next/master, in case you haven't.
I will rebase on linux-next/master in future patch work.
Thanks,
Liang
Quoted 2 lines · Liang He
At 2022-07-18 15:08:48, "Viresh Kumar" <[email protected]> wrote:
But is it OK if the two patches change the same file at same time?
Yes.
Quoted 1 line
I wonder if this will trouble you to merge them later.
If I apply the patches in the same order you send them (based on patch numbers in subject), it will never be a problem.
Quoted 2 lines
After I read the code, I think it is better to drop
opp_table->npin '_opp_table_kref_release' just like we do for the 'opp->np' in '_opp_kref_release'.
Yeah, look fine, though a review after the new version will make it more clear.
Signature · 1 line
viresh