linux-kernel - Re: OOM-killer and strange RSS value in 3.9-rc7

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: <20130422031504.GF2672@localhost.localdomain>
Date:	Mon, 22 Apr 2013 11:15:04 +0800
From:	Han Pingtian <hanpt@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	jkosina@...e.cz, rientjes@...gle.com, mhocko@...e.cz
Subject: Re: OOM-killer and strange RSS value in 3.9-rc7

On Sun, Apr 21, 2013 at 02:49:31AM +0200, Jiri Kosina wrote:
> On Wed, 17 Apr 2013, Han Pingtian wrote:
> 
> > > > On a power7 system, we have installed 3.9-rc7 and crash 6.1.6. If I run
> > > > something like "make -j 64" to compile linux kernel from source, sooner
> > > > or latter, oom-killer will be triggered. Before that, when I trying to
> > > > analyse the live system with crash, some processes' %MEM and RSS looks
> > > > too big:
> > > > 
> > > 
> > > Do you have the oom killer log from /var/log/messages with 
> > > /proc/sys/vm/oom_dump_tasks enabled?  Have you tried to reproduce this 
> > > issue with CONFIG_DEBUG_VM and CONFIG_DEBUG_PAGEALLOC enabled (you may 
> > > even want to consider CONFIG_KMEMLEAK)?
> > 
> > I have enabled CONFIG_KMEMLEAK and recompiled kernel. This is the
> > /sys/kernel/debug/kmemleak after the reboot. Please have a look. Thanks.
> 
> Either kmemleak is very wrong about some false positive in selinux, or 
> selinux is leaking memory quite heavily.
> 
> Could you try disabling selinux completely, to see if the leak goes away?
> 
Thanks your reply. We had disable selinux from the very beginning.

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