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
| ||
|
Date: Wed, 22 Oct 2014 16:28:14 +0200 From: Daniel Lezcano <daniel.lezcano@...aro.org> To: Jiri Kosina <jkosina@...e.cz>, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, "Rafael J. Wysocki" <rjw@...ysocki.net>, Pavel Machek <pavel@....cz>, Steven Rostedt <rostedt@...dmis.org>, Dave Jones <davej@...hat.com>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Nicolas Pitre <nico@...aro.org> CC: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org Subject: Re: lockdep splat in CPU hotplug On 10/22/2014 11:53 AM, Jiri Kosina wrote: > On Tue, 21 Oct 2014, Jiri Kosina wrote: > >> Hi, >> >> I am seeing the lockdep report below when resuming from suspend-to-disk >> with current Linus' tree (c2661b80609). >> >> The reason for CCing Ingo and Peter is that I can't make any sense of one >> of the stacktraces lockdep is providing. >> >> Please have a look at the very first stacktrace in the dump, where lockdep >> is trying to explain where cpu_hotplug.lock#2 has been acquired. It seems >> to imply that cpuidle_pause() is taking cpu_hotplug.lock, but that's not >> the case at all. >> >> What am I missing? > > Okay, reverting 442bf3aaf55a ("sched: Let the scheduler see CPU idle > states") and followup 83a0a96a5f26 ("sched/fair: Leverage the idle state > info when choosing the "idlest" cpu") which depends on it makes the splat > go away. Are you able to reproduce it by offlining the cpu and onlining it again ? -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog -- 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