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

Date:	Tue, 1 Apr 2014 16:04: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:59:06PM +0200, Paul Bolle wrote:
> On Tue, 2014-04-01 at 13:52 -0700, Paul E. McKenney wrote:
> > I don't believe that this is particularly urgent, so unless someone
> > tells me otherwise, I will queue the fix for 3.16.
> 
> Few people share my OCD for Kconfig symbols. So most people will not
> think this is urgent. On the other hand, why wait three to four months
> when this can be cleaned up in a few weeks?

Because I need to decide whether the right fix is to add the
LOCK_TORTURE_RUNNABLE or to remove the RCU_TORTURE_RUNNABLE.  ;-)

My kneejerk reaction was the former, but I am leaning towards the latter.
Shrinks the code a bit, gets rid of a Kconfig parameter and only requires
changes in scripts for a few people using rcutorture...

							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/