linux-kernel - Re: [Bug #30572] 2.6.38-rc7, OOM 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.1103281535130.7148@chino.kir.corp.google.com>
Date:	Mon, 28 Mar 2011 15:37:23 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Mathias Burén <mathias.buren@...il.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Florian Mickler <florian@...kler.org>
Subject: Re: [Bug #30572] 2.6.38-rc7, OOM behaviour?

On Sun, 27 Mar 2011, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.37.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=30572
> Subject		: 2.6.38-rc7, OOM behaviour?
> Submitter	: Mathias Burén <mathias.buren@...il.com>
> Date		: 2011-03-02 19:33 (26 days old)
> Message-ID	: <AANLkTine5sru_JsK1LmRVa9fwxjPsaDdZUTFPCBi6A+c@...l.gmail.com>
> References	: http://marc.info/?l=linux-kernel&m=129909440018096&w=2
> 

The log that was presented in the References link is a normal oom killer 
log and would be typical if you exhausted 1GB of swap space.  It correctly 
kills the chrome process in the log provided, but other relevant portions 
seem to have been snipped for futher diagnosis.

Mathias, could you please provide the entire oom killer output, 
specifically the last time it was invoked (search for "invoked 
oom\-killer" and paste everything after the last occurrence)?