public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kevin O'Connor" <kevin@koconnor.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
	sds@epoch.ncsc.mil, jmorris@namei.org
Subject: Re: Size-128 slab leak
Date: Thu, 2 Feb 2006 23:00:18 -0500	[thread overview]
Message-ID: <20060203040018.GA3757@double.lan> (raw)
In-Reply-To: <20060201231001.0ca96bf0.akpm@osdl.org>

On Wed, Feb 01, 2006 at 11:10:01PM -0800, Andrew Morton wrote:
> "Kevin O'Connor" <kevin@koconnor.net> wrote:
> >
> > I have an annoying slab leak on my kernel.  Every day, I lose about
> >  50Megs of memory to the leak.  It seems to be related to disk
> >  accesses, because the count only goes up noticeable around 4:00am when
> >  the system locate utility runs.
> > 
> >  I can tell there is a leak because /proc/slabinfo shows "size-128"
> >  growing continuously.  For example, it currently reads:
>
> -mm kernels have a patch (slab-leak-detector.patch) which will help. 
> Here's a version for 2.6.16-rc1.  It requires CONFIG_DEBUG_SLAB.  Thanks.

Thanks Andrew.

I've applied the patch and found the leak.  It's in kzalloc.  :-)

With kzalloc inlined, however, it appears that selinux is the likely
culprit.  I would not have expected that.

After running updatedb I got 23530 occurrences of:

kernel: obj ffff81003f04f000/12: ffffffff801ed7b7 <selinux_inode_alloc_security+0x37/0x100>

I'm not sure how to debug selinux issues, but at least I can disable
it.

-Kevin

  parent reply	other threads:[~2006-02-03  4:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  2:49 Size-128 slab leak Kevin O'Connor
2006-02-02  7:10 ` Andrew Morton
2006-02-02  7:32   ` Pekka Enberg
2006-02-03  6:21     ` Manfred Spraul
2006-02-03  4:00   ` Kevin O'Connor [this message]
2006-02-03 13:21     ` Stephen Smalley
2006-02-03 15:13       ` James Morris
2006-02-04  1:13       ` Kevin O'Connor
2006-02-14  4:52       ` Jeffrey Mahoney

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=20060203040018.GA3757@double.lan \
    --to=kevin@koconnor.net \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /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