public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: jkosina@suse.cz, rientjes@google.com, mhocko@suse.cz
Subject: Re: OOM-killer and strange RSS value in 3.9-rc7
Date: Mon, 22 Apr 2013 11:15:04 +0800	[thread overview]
Message-ID: <20130422031504.GF2672@localhost.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.00.1304210247270.15075@twin.jikos.cz>

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.


  reply	other threads:[~2013-04-22  3:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 11:00 OOM-killer and strange RSS value in 3.9-rc7 Han Pingtian
2013-04-16 20:16 ` David Rientjes
2013-04-17  8:46   ` Han Pingtian
2013-04-21  0:49     ` Jiri Kosina
2013-04-22  3:15       ` Han Pingtian [this message]
2013-04-17  9:47   ` Han Pingtian
2013-04-17 14:19     ` Michal Hocko
2013-04-18 10:15       ` Han Pingtian
2013-04-18 14:17         ` Michal Hocko
2013-04-18 16:55           ` Han Pingtian
2013-04-18 17:55             ` Michal Hocko
2013-04-19  2:33               ` Han Pingtian
2013-04-19 16:43                 ` Michal Hocko
2013-04-22  3:18                   ` Han Pingtian
2013-04-22 11:40                     ` Michal Hocko
2013-04-23  4:22                       ` Han Pingtian
2013-04-23 13:15                         ` Michal Hocko
2013-04-24  4:48                           ` Han Pingtian
2013-04-24  9:47                             ` Michal Hocko
2013-04-24 15:36                               ` Christoph Lameter
2013-04-25  6:07                                 ` Han Pingtian
2013-04-25 17:17                                   ` Christoph Lameter
2013-04-27  8:20                                     ` Will Huck
2013-04-29 14:49                                       ` Christoph Lameter
2013-05-01  3:13                                         ` Will Huck
2013-05-02 15:10                                           ` Christoph Lameter
2013-04-25 18:24                                   ` Christoph Lameter
2013-04-26  6:24                                     ` Han Pingtian
2013-04-26 14:42                                       ` Christoph Lameter
2013-04-27 11:24                                         ` Han Pingtian
2013-04-29 14:50                                           ` Christoph Lameter
2013-04-29 14:57                                             ` Michal Hocko
2013-05-02 10:56                                               ` Han Pingtian
2013-05-02 15:10                                                 ` Christoph Lameter
2013-05-03  3:03                                                   ` Han Pingtian
2013-05-03 15:25                                                     ` Christoph Lameter
2013-05-03 15:34                                                       ` Michal Hocko
2013-05-03 16:16                                                         ` Christoph Lameter
     [not found]                                                           ` <52bd58da.2501440a.6368.16ddSMTPIN_ADDED_BROKEN@mx.google.com>
     [not found]                                                             ` <52caac5c.27cb440a.533d.ffffbbd2SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-21 22:12                                                               ` David Rientjes
2013-04-25  5:41                               ` Han Pingtian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130422031504.GF2672@localhost.localdomain \
    --to=hanpt@linux.vnet.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox