linux-kernel - Re: [patch 03/18] fork: Move thread info gfp flags to header

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: <20120508175105.GA18741@linux.vnet.ibm.com>
Date:	Tue, 8 May 2012 10:51:05 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 03/18] fork: Move thread info gfp flags to header

On Mon, May 07, 2012 at 01:53:21PM -0700, Paul E. McKenney wrote:
> On Mon, May 07, 2012 at 09:14:04PM +0200, Thomas Gleixner wrote:
> > On Sun, 6 May 2012, Paul E. McKenney wrote:
> > 
> > > On Sat, May 05, 2012 at 03:05:41PM -0000, Thomas Gleixner wrote:
> > > > These flags can be useful for extra allocations outside of the core
> > > > code.
> > > > 
> > > > Add __GFP_NOTRACE to them, so the archs which have kmemcheck do
> > > > not have to provide extra allocators just for that reason.
> > > 
> > > This breaks powerpc builds due to __GFP_NOTRACE not being defined.
> > > I restarted the test after removing the __GFP_NOTRACE as a testing-only
> > > hack, and will let you know how it goes.  Also looking into why this
> > > builds on 32-bit x86 but not on powerpc.
> > 
> > Hrmpf. Seems the idiot I am fatfingered __GFP_NOTRACK to __GFP_NOTRACE
> > and then only tested with the DEBUG stuff disabled......
> 
> That sounds like something I would do...  ;-)
> 
> I will rerun with __GFP_NOTRACK.

Which passes moderate rcutorture testing on Power.

							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/