linux-kernel - Re: OOM kernel behaviour

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.0912011124490.10426@router.home>
Date:	Tue, 1 Dec 2009 11:26:37 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Mel Gorman <mel@....ul.ie>
cc:	David John <davidjon@...ontk.org>, linux-kernel@...r.kernel.org,
	Jonathan Miles <jon@...us.co.uk>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: OOM kernel behaviour

On Tue, 1 Dec 2009, David John wrote:

> Here are three logs from three days. Log3.txt is today's log and the OOM
> killer murdered Thunderbird as I was attempting to write this message.
> The kernel config is also attached.

Hmmm... This is all caused by the HIGHMEM zone freecount going beyond min
which then triggers reclaim which for some reason fails (should not there
is sufficient material there to reclaim). There is enough memory in the
NORMAL zone. Wonder if something broke in 2.6.31 in reclaim? Mel?

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