Re: PM / devfreq: map devfreq drivers to governor using name

2020-10-28 Thread Colin Ian King
Mon Oct 29 15:01:45 2012 -0500 > > PM / devfreq: map devfreq drivers to governor using name > > > The analysis is as follows for devfreq_remove_governor in > drivers/devfreq/devfreq.c > > 1312 > > deref_ptr_in_call: Dereferencing pointer devfreq->governor. >

re: PM / devfreq: map devfreq drivers to governor using name

2020-10-28 Thread Colin Ian King
Hi, Static analysis of linux-next with Coverity has found a potential null pointer dereference issue with the following commit: commit 1b5c1be2c88e8445a20fa1929e26c37e7ca8c926 Author: Nishanth Menon Date: Mon Oct 29 15:01:45 2012 -0500 PM / devfreq: map devfreq drivers to governor using

[linux-next PATCH 4/7] PM / devfreq: map devfreq drivers to governor using name

2012-10-29 Thread Nishanth Menon
Allow devfreq drivers to register a preferred governor name and when the devfreq governor loads itself at a later point required drivers are managed appropriately, at the time of unload of a devfreq governor, stop managing those drivers as well. Since the governor structures do not need to be

[linux-next PATCH 4/7] PM / devfreq: map devfreq drivers to governor using name

2012-10-29 Thread Nishanth Menon
Allow devfreq drivers to register a preferred governor name and when the devfreq governor loads itself at a later point required drivers are managed appropriately, at the time of unload of a devfreq governor, stop managing those drivers as well. Since the governor structures do not need to be