| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <3547840.51rbRs871Y@vostro.rjw.lan> Date: Thu, 16 Jul 2015 02:32:14 +0200 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Viresh Kumar <viresh.kumar@...aro.org> Cc: "Jon Medhurst (Tixy)" <tixy@...aro.org>, linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/2] cpufreq: Properly handle errors from cpufreq_init_policy() On Wednesday, July 08, 2015 04:50:23 PM Viresh Kumar wrote: > On 08-07-15, 12:17, Jon Medhurst (Tixy) wrote: > > I tried these patches without the earlier "cpufreq: Initialize the > > governor again while restoring policy" patch. > > > > The result is that the error when bringing a cpu online is with flagged > > up with a kernel message: > > > > cpufreq: cpufreq_add_dev: Failed to initialize policy for cpu: 1 (-16) > > > > and afterwards, the sysfs entries that I was poking and causing the > > crash aren't present. So looks like this patch has done what we want, > > and cleaned things up after an error. So... > > > > Tested-by: Jon Medhurst <tixy@...aro.org> > > > > Thanks for the prompt fix. > > And thanks for your help in getting these tested :) Both queued up for 4.3, thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists