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  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:	Sun, 21 Apr 2013 02:49:31 +0200 (CEST)
From:	Jiri Kosina <>
To:	Han Pingtian <>
Cc:, David Rientjes <>,
	Michal Hocko <>
Subject: Re: OOM-killer and strange RSS value in 3.9-rc7

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?

Jiri Kosina

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists