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: <4B1C93E0.4070806@xenontk.org>
Date:	Mon, 07 Dec 2009 11:04:24 +0530
From:	David John <davidjon@...ontk.org>
To:	Mel Gorman <mel@....ul.ie>
CC:	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Jonathan Miles <jon@...us.co.uk>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: OOM kernel behaviour

On 12/02/2009 09:25 PM, Mel Gorman wrote:
> On Tue, Dec 01, 2009 at 11:26:37AM -0600, Christoph Lameter wrote:
>> 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?
>>
> 
> I'm not aware of breakage of that level, nor do I believe the page
> allocator problems are related to this bug.
> 
> However, I just took a look at the logs from the three days and I see
> things like
> 
> Nov 25 23:58:53 avalanche kernel: Free swap  = 0kB
> Nov 25 23:58:53 avalanche kernel: Total swap = 2048248kB
> 
> 
> Something on that system is leaking badly. Do something like
> 
> ps aux --sort vsz
> 
> and see what process has gone mental and is consuming all of swap. It's
> possible that the OOM killer is triggering too easily but it's possible
> that a delayed triggering of the OOM killer would have been just that -
> a delay. Eventually all memory and all swap would be used.
> 

Hi All,

It is a leak in Compiz. Killing and restarting Compiz frees up the swap.
The issue is better in 2.6.32 for some reason. The funny thing is I've
been using Compiz with 2.6.31 for a couple of months now, with no
updates to either, so I'm not sure what triggered this problem.

Regards,
David.
--
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/