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, 16 Jul 2014 22:33:34 -0700 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Sasha Levin <sasha.levin@...cle.com> Cc: linux-kernel@...r.kernel.org, mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com, akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com, josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com, sbw@....edu, linux-rt-users@...r.kernel.org Subject: Re: [PATCH RFC tip/core/rcu 1/2] rcu: Rationalize kthread spawning On Wed, Jul 16, 2014 at 10:57:39PM -0400, Sasha Levin wrote: > On 07/14/2014 06:06 AM, Paul E. McKenney wrote: > > From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> > > > > Currently, RCU spawns kthreads from several different early_initcall() > > functions. Although this has served RCU well for quite some time, > > as more kthreads are added a more deterministic approach is required. > > This commit therefore causes all of RCU's early-boot kthreads to be > > spawned from a single early_initcall() function. > > > > Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com> > > Hey Paul, > > I've updated to today's -next and my VM started hanging on boot. Bisect > pointed out this patch. > > I don't have any further info right now, but can provide whatever you'll > find useful. Could you please add initcall_debug to qemu's -append list? If sysrq-T works that early, its output would be helpful as well. Your .config would also be helpful. Thanx, Paul -- 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