Skip to content

Commit b19c235

Browse files
committed
opp: Reinitialize the list_kref before adding the static OPPs again
The list_kref reaches a count of 0 when all the static OPPs are removed, for example when dev_pm_opp_of_cpumask_remove_table() is called, though the actual OPP table may not get freed as it may still be referenced by other parts of the kernel, like from a call to dev_pm_opp_set_supported_hw(). And if we call dev_pm_opp_of_cpumask_add_table() again at this point, we must reinitialize the list_kref otherwise the kernel will hit a WARN() in kref infrastructure for incrementing a kref with value 0. Fixes: 11e1a16 ("opp: Don't decrement uninitialized list_kref") Reported-by: Dmitry Osipenko <[email protected]> Tested-by: Dmitry Osipenko <[email protected]> Signed-off-by: Viresh Kumar <[email protected]>
1 parent 24957db commit b19c235

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

drivers/opp/of.c

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -663,6 +663,13 @@ static int _of_add_opp_table_v2(struct device *dev, struct opp_table *opp_table)
663663
return 0;
664664
}
665665

666+
/*
667+
* Re-initialize list_kref every time we add static OPPs to the OPP
668+
* table as the reference count may be 0 after the last tie static OPPs
669+
* were removed.
670+
*/
671+
kref_init(&opp_table->list_kref);
672+
666673
/* We have opp-table node now, iterate over it and add OPPs */
667674
for_each_available_child_of_node(opp_table->np, np) {
668675
opp = _opp_add_static_v2(opp_table, dev, np);

0 commit comments

Comments
 (0)