linux-kernel - Re: [GIT PULL] RCU changes for v3.15

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140401205219.GX4284@linux.vnet.ibm.com>
Date:	Tue, 1 Apr 2014 13:52:19 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v3.15

On Tue, Apr 01, 2014 at 10:31:31PM +0200, Paul Bolle wrote:
> > Paul E. McKenney (70):
> >      [...]
> >       locktorture: Add a lock-torture kernel module
> 
> This commit added a check for CONFIG_LOCK_TORTURE_TEST_RUNNABLE. But I
> can't find a Kconfig symbol LOCK_TORTURE_TEST_RUNNABLE nor a
> preprocessor define for CONFIG_LOCK_TORTURE_TEST_RUNNABLE. (I only
> checked master of Linus's tree and linux-next.)
> 
> Is this check for CONFIG_LOCK_TORTURE_TEST_RUNNABLE needed?

My bad.  My current tests use the boot parameter rather than relying on
the Kconfig parameter, so I missed this bug.  I will of course fix it.
I don't believe that this is particularly urgent, so unless someone
tells me otherwise, I will queue the fix for 3.16.

							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/