linux-kernel - Re: 2.6.22-stable causes oomkiller to be invoked

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:	Fri, 14 Dec 2007 21:46:37 +0530
From:	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
To:	Tejun Heo <htejun@...il.com>
Cc:	Greg KH <gregkh@...e.de>, stable@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>, maneesh@...ux.vnet.ibm.com,
	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
	Balbir Singh <balbir@...ibm.com>,
	Gautham Shenoy <ego@...ibm.com>
Subject: Re: 2.6.22-stable causes oomkiller to be invoked

On Sat, Dec 15, 2007 at 12:54:09AM +0900, Tejun Heo wrote:
> Dhaval Giani wrote:
> > XXX sysfs_page_cnt=1
> 
> Hmm.. so, sysfs r/w buffer wasn't the culprit.  I'm curious what eats up
> all your low memory.  Please do the following.
> 
> 1. Right after boot, record /proc/meminfo and slabinfo.
> 
> 2. After or near OOM, record /proc/meminfo and slabinfo.  This can be
> tricky but if your machine reliably OOMs after 10mins, run it for 9mins
> and capturing the result should show enough.
> 

Attached. The results are after oom, but i think about a min or so after
that. I missed the oom point.

-- 
regards,
Dhaval

View attachment "meminfo-boot" of type "text/plain" (846 bytes)

View attachment "meminfo-oom" of type "text/plain" (846 bytes)

View attachment "slabinfo-boot" of type "text/plain" (30018 bytes)

View attachment "slabinfo-oom" of type "text/plain" (30029 bytes)