| 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: Tue, 15 May 2007 23:42:31 -0700 From: Josh Triplett <josh@...nel.org> To: paulmck@...ux.vnet.ibm.com CC: linux-kernel@...r.kernel.org, ak@...e.de, akpm@...ux-foundation.org, dipankar@...ibm.com, randy.dunlap@...cle.com Subject: Re: [PATCH] prohibit rcutorture from being compiled into the kernel Paul E. McKenney wrote: > There have been a number of instances where people have accidentally > compiled rcutorture into the kernel (CONFIG_RCU_TORTURE_TEST=y), which > has never been useful, and has often resulted in great frustration. The > attached patch prohibits rcutorture from being compiled into the kernel. > It may be excluded altogether or compiled as a module. People wishing > to have rcutorture hammer their machine immediately upon boot are free > to hand-edit lib/Kconfig.debug to remove the "depends on m" line. > > Thanks to Randy Dunlap for the trick that makes this work. > > Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com> This seems reasonable to me. I can imagine legitimate reasons to want to have rcutorture running as early as possible, but as you said, anyone wishing to do so can hand-edit lib/Kconfig.debug easily enough. Acked-by: Josh Triplett <josh@...nel.org> - Josh Triplett - 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