linux-kernel - Re: Found the commit that causes the OOMs

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]

Date:	Tue, 30 Jun 2009 20:57:47 +0100
From:	David Howells <dhowells@...hat.com>
To:	Minchan Kim <minchan.kim@...il.com>
Cc:	dhowells@...hat.com, Mel Gorman <mel@....ul.ie>,
	Wu Fengguang <fengguang.wu@...el.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Johannes Weiner <hannes@...xchg.org>,
	"riel\@redhat.com" <riel@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Lameter <cl@...ux-foundation.org>,
	"peterz\@infradead.org" <peterz@...radead.org>,
	"tytso\@mit.edu" <tytso@....edu>,
	"linux-mm\@kvack.org" <linux-mm@...ck.org>,
	"elladan\@eskimo.com" <elladan@...imo.com>,
	"npiggin\@suse.de" <npiggin@...e.de>,
	"Barnes\, Jesse" <jesse.barnes@...el.com>
Subject: Re: Found the commit that causes the OOMs

Minchan Kim <minchan.kim@...il.com> wrote:

> David. Doesn't it happen OOM if you revert my patch, still?

It does happen, and indeed happens in v2.6.30, but requires two adjacent runs
of msgctl11 to trigger, rather than usually triggering on the first run.  If
you interpolate the rest of LTP between the iterations, it doesn't seem to
happen at all on v2.6.30.  My guess is that with the rest of LTP interpolated,
there's either enough time for some cleanup or something triggers a cleanup
(the swapfile tests perhaps?).

> Befor I go to the trip, I made debugging patch in a hurry.  Mel and I
> suspect to put the wrong page in lru list.
> 
> This patch's goal is that print page's detail on active anon lru when it
> happen OOM.  Maybe you could expand your log buffer size.

Do you mean to expand the dmesg buffer?  That's probably unnecessary: I capture
the kernel log over a serial port into a file on another machine.

> Could you show me the information with OOM, please ?

Attached.  It's compressed as there was rather a lot.

David
---

Download attachment "oom.log.bz2" of type "application/x-bzip2" (166471 bytes)