linux-kernel - Re: Odd Kconfig output..

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 8 Sep 2009 15:09:43 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Valdis.Kletnieks@...edu
Cc:	Roman Zippel <zippel@...ux-m68k.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: Odd Kconfig output..

On Sat, Sep 05, 2009 at 09:06:14AM -0400, Valdis.Kletnieks@...edu wrote:
> Saw this while doing  a 'make oldconfig' moving from -mmotm0827 to -mmotm0903:
> 
> RCU Implementation
> > 1. Tree-based hierarchical RCU (TREE_RCU)
>   2. Preemptable tree-based hierarchical RCU (TREE_PREEMPT_RCU) (NEW)
> choice[1-2]: ?
> 
> There is no help available for this kernel option.
> Prompt: RCU Implementation
>   Defined at init/Kconfig:329
>   Location:
>     -> General setup
>       -> RCU Subsystem
>   Selected by: m [=m]
> 
> Where did that 'Selected by:' come from? Or is that just an artifact of
> the way Kconfig implements 'choice'?

Many of the architectures use a "select" clause for RCU, usually
selecting CLASSIC_RCU.  Could that be the issue?

							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/