Re: [PATCH] cpufreq: Initialize the governor again while restoring policy

On 08-07-15, 10:27, Jon Medhurst (Tixy) wrote:

I believe this also fixes the other issue I mentioned (nullptr deref in in arm_big_little driver). To test that, after applying this patch, I modified the code to force __cpufreq_governor to still return an error when a cpu is hotpluged back in. Now the arm_big_little driver doesn't get called when I manually poke scaling_setspeed, presumably because policy->governor==NULL prevents that from reaching the driver?

I would like to fix that issue without using this patch as we aren't cleaning up things properly on errors today. I am almost done with the patches, and will send them to you shortly. Please give them a try without this patch.