| 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: <1306345492.21978.15.camel@t41.thuisdomein> Date: Wed, 25 May 2011 19:44:51 +0200 From: Paul Bolle <pebolle@...cali.nl> To: paulmck@...ux.vnet.ibm.com Cc: Vivek Goyal <vgoyal@...hat.com>, Jens Axboe <jaxboe@...ionio.com>, linux kernel mailing list <linux-kernel@...r.kernel.org> Subject: Re: Mysterious CFQ crash and RCU On Wed, 2011-05-25 at 08:33 -0700, Paul E. McKenney wrote: > On Wed, May 25, 2011 at 12:17:16PM +0200, Paul Bolle wrote: > > 2) So shouldn't either the config entry be set to "tristate" or the > > module support removed from kernel/rcutree_trace.c? > > No. > > Just set CONFIG_RCU_TRACE=y and you will have RCU tracing. Here is why: > >[...] > > So you can set CONFIG_RCU_TRACE, and if you are running CONFIG_SMP=y, > you will have RCU tracing in your kernel. The point - which I must have expressed poorly - is that there's a mismatch between the code in kernel/rcutree_trace.c (which allows for that file to be built as a module) and its kconfig setup (which requires it to be either builtin or not built at all, since it's boolean). Anyhow, your explanation makes clear that this kconfig setup is actually correct and that the module support in kernel/rcutree_trace.c might as well be removed, since that file can never be part of a module. Paul Bolle -- 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