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: Mon, 28 Jul 2008 15:50:04 -0700 From: Jeremy Fitzhardinge <jeremy@...p.org> To: David Miller <davem@...emloft.net> CC: mingo@...e.hu, peterz@...radead.org, linux-kernel@...r.kernel.org, Rusty Russell <rusty@...tcorp.com.au> Subject: Re: combinatorial explosion in lockdep David Miller wrote: > The triggering event seems to be kstopmachine as done by the first > module load. This seems to create the situation where we do double RQ > locking on essentially all the run queues, in order to move the > kstopmachine threads around to their proprer cpus. I think this is > what starts to make the lockdep dependency chains huge. > Does Rusty's stop_machine rewrite which puts the threads on the correct cpus to start with at least mitigate the symptoms? J -- 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