linux-kernel - Re: [patch -mmotm] mm: invoke oom killer for __GFP

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, 12 May 2009 19:35:16 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	David Rientjes <rientjes@...gle.com>, mel@....ul.ie,
	a.p.zijlstra@...llo.nl, cl@...ux-foundation.org,
	dave@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	Divy Le Ray <divy@...lsio.com>
Subject: Re: [patch -mmotm] mm: invoke oom killer for __GFP_NOFAIL

On Tue, May 12 2009, Nick Piggin wrote:
> On Tue, May 12, 2009 at 06:37:30PM +0200, Jens Axboe wrote:
> > On Tue, May 12 2009, Nick Piggin wrote:
> > > On Tue, May 12, 2009 at 02:42:02PM +0200, Jens Axboe wrote:
> > > > On Mon, May 11 2009, Andrew Morton wrote:
> > > > > On Sat, 9 May 2009 15:46:39 -0700 (PDT)
> > > > > David Rientjes <rientjes@...gle.com> wrote:
> > > > > 
> > > > > > The oom killer must be invoked regardless of the order if the allocation
> > > > > > is __GFP_NOFAIL, otherwise it will loop forever when reclaim fails to
> > > > > > free some memory.
> > > > > 
> > > > > Sigh.  We're supposed to be deleting __GFP_NOFAIL.  I added it as a way
> > > > > of easily finding lame error-handling-challenged callers which need to
> > > > > be fixed up.  So of course we went and added lots more callers.
> > > > > 
> > > > > y:/usr/src/linux-2.6.30-rc5> grep -rl GFP_NOFAIL . 
> > > > > ./fs/bio-integrity.c
> > > 
> > > This is no good either, it seems to be in the bio submission path.
> > > 
> > > It needs a mempool or something.
> > 
> > mempool cannot help here, since the allocation is tied to the process
> > (and IO) life time.
> 
> Oh, I was talking about bio-integrity.c...

Oops my bad, I was on the (apparently) cfq case. I agree on the
integrity path, a mempool should work fine for that.

-- 
Jens Axboe

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