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: <alpine.DEB.2.00.1008241210570.3695@router.home>
Date:	Tue, 24 Aug 2010 12:13:23 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Stan Hoeppner <stan@...dwarefreak.com>
cc:	Pekka Enberg <penberg@...nel.org>,
	Mikael Abrahamsson <swmike@....pp.se>,
	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 Mon, 23 Aug 2010, Stan Hoeppner wrote:

> Should I be using SLUB instead?  Any downsides to SLUB on an old and
> slow (500 MHz) single core dual CPU box with <512MB RAM?

SLUB has a smaller memory footprint so you may come out ahead for
such a small system in particular.

> Also, what is the impact of these oopses?  Despite the entries in dmesg,
> the system "seems" to be running ok.  Or is this simply the calm before
> the impending storm?

The system does not guarantee that GFP_ATOMIC allocation succeed so any
caller must provide logic to fall back if no memory is allocated. So the
effect may just be that certain OS operations have to be retried.


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