linux-kernel - Re: 2.6.34.1 page allocation failure

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: <4C724141.8060000@kernel.org>
Date:	Mon, 23 Aug 2010 12:37:05 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Christoph Lameter <cl@...ux.com>
CC:	Mikael Abrahamsson <swmike@....pp.se>,
	Stan Hoeppner <stan@...dwarefreak.com>,
	Linux Kernel List <linux-kernel@...r.kernel.org>,
	linux-mm@...ck.org, Mel Gorman <mel@....ul.ie>
Subject: Re: 2.6.34.1 page allocation failure

  On 8/23/10 1:40 AM, Christoph Lameter wrote:
> On Sun, 22 Aug 2010, Pekka Enberg wrote:
>
>> In Stan's case, it's a order-1 GFP_ATOMIC allocation but there are
>> only order-0 pages available. Mel, any recent page allocator fixes in
>> 2.6.35 or 2.6.36-rc1 that Stan/Mikael should test?
> This is the TCP slab? Best fix would be in the page allocator. However,
> in this particular case the slub allocator would be able to fall back to
> an order 0 allocation and still satisfy the request.
>
Looking at the stack trace of the oops, I think Stan has CONFIG_SLAB 
which doesn't have order-0 fallback.

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