linux-kernel - Re: [bug?] bio: add experimental support for inlining a number of bio

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: <20081211073226.GW23742@kernel.dk>
Date:	Thu, 11 Dec 2008 08:32:28 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	kosaki.motohiro@...fujitsu.com, sfr@...b.auug.org.au,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [bug?] bio: add experimental support for inlining a number of bio_vecs inside the bio

On Wed, Dec 10 2008, Andrew Morton wrote:
> On Wed, 10 Dec 2008 13:12:38 +0100
> Jens Axboe <jens.axboe@...cle.com> wrote:
> 
> > > experimental??
> > 
> > Experimental in the sense that it's the first version, not the concept.
> > It's held up well for me, but just yesterday I received the first bug
> > report on a ppc platform and now you have this on ia64.
> 
> 
> Well there's another bug report up-list.  "next-20081209: pdflush: page
> allocation failure (xfs)".
> 
> The clearing of (__GFP_WAIT | __GFP_IO) will call the page allocator in the
> weakest possible mode and will of course spew page allocations warnings
> with great frequency.  It should at least add in __GFP_NOWARN.

OK, that must be for the change titled

"bio: only mempool back the largest bio_vec slab cache"

and yes, that does look like it wants a bit more gfp loving, probably
the same as mempool_alloc() would use anyway. I'll get that fixed.

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