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: <4B1972B6.1060408@cybus.co.uk>
Date:	Fri, 04 Dec 2009 20:36:06 +0000
From:	Jonathan Miles <jon@...us.co.uk>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, David John <davidjon@...ontk.org>,
	penberg@...helsinki.fi
Subject: Re: OOM kernel behaviour - 2.6.32

On 01/12/09 18:07 Jonathan Miles said the following:

> It's Ubuntu's (Karmic) 2.6.31 .deb and I don't know exactly what they've
> done to it, but AFAIK, no containers or policies. I'll compile 2.6.31.6
> and test with that. Won't be able to do this until Friday, so will check
> back in then.

Everything is fine having compiled straight 2.6.32. I watched the cache
being reclaimed with top as I used more and more RAM and didn't see the
OOM killer being invoked. So it was either a problem with 2.6.31 or with
whatever Ubuntu did to make the .deb.

Thanks,

-- 
Jonathan Miles <jon@...us.co.uk>
http://www.linkedin.com/in/jonmiles

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