linux-kernel - Re: [PATCH] use GFP_NOFS in kernel

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: <20090501132818.b16704c4.akpm@linux-foundation.org>
Date:	Fri, 1 May 2009 13:28:18 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	fengguang.wu@...el.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, mpm@...enic.com, clameter@....com,
	mingo@...e.hu, viro@...iv.linux.org.uk
Subject: Re: [PATCH] use GFP_NOFS in kernel_event()

On Fri, 01 May 2009 14:11:34 -0400
Eric Paris <eparis@...hat.com> wrote:

> On Thu, 2009-04-30 at 14:10 -0700, Andrew Morton wrote:
> > On Thu, 30 Apr 2009 09:19:33 -0400
> > Eric Paris <eparis@...hat.com> wrote:
> > 
> > > > Somebody was going to fix this for us via lockdep annotation.
> > > > 
> > > > <adds randomly-chosen cc>
> > > 
> > > I really didn't forget this, but I can't figure out how to recreate it,
> > > so I don't know if my logic in the patch is sound.  The patch certainly
> > > will shut up the complaint.
> > 
> > Do you think we should merge the GFP_NOFS workaround for 2.6.30 and
> > fix all up nicely for 2.6.31?
> 
> I'm all for it for 2.6.30

OK.

> although the patch really should have been
> the one that gets the audit use case too at 
> 
> >From me on Mar 18 Subject [PATCH] make inotify event handles use
> GFP_NOFS
> 
> http://lkml.org/lkml/2009/3/18/310

I queued that as an incremental to Wu Fengguang's patch, because
inotify-use-gfp_nofs-in-kernel_event-to-work-around-a-lockdep-false-positive.patch
has a longer changelog ;)

--
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/