All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Johns Daniel <johns.daniel@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Slab memory leak in JFFS2 filesystems
Date: Fri, 25 Feb 2011 18:27:58 +0200	[thread overview]
Message-ID: <1298651278.2346.2.camel@koala> (raw)
In-Reply-To: <AANLkTimvqdu1k3ZL4rqC-DBiMkNmytBXZ1YWXNE0Gs6F@mail.gmail.com>

On Fri, 2011-02-25 at 10:12 -0600, Johns Daniel wrote:
> On Fri, Feb 25, 2011 at 6:38 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Thu, 2011-02-24 at 18:41 -0600, Johns Daniel wrote:
> >> I have discovered a kernel memory leak associated with JFFS2
> >> filesystems. I have verified the leak in kernels 2.6.28 and 2.6.36 on
> >> a Freescale PowerPC board using this script:
> >>
> >> while :; do FN=$(mktemp /jffs2fs/TMP.XXXXXXXX); \
> >>    cat /proc/slabinfo |grep "dentry\|size-64 "; sleep 1; /bin/rm $FN; done
> >
> > Please, check whether they go away after:
> >
> > echo 3 > /proc/sys/vm/drop_caches
> >
> > See Documentation/sysctl/vm.txt for more information about what this
> > means.
> 
> Thanks for that suggestion, Artem! Here is what I tried:

Hi, you can try to play with kmemleak - this is a kernel feature which
slows down the system a lot but is great in catching memory leaks. It
may have false positives sometimes, though. You can read about kmemleak
in the Documentation/ directory. I think if there are leaks in JFFS2 -
kmemleak would spot them.

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2011-02-25 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  0:41 Slab memory leak in JFFS2 filesystems Johns Daniel
2011-02-25 12:38 ` Artem Bityutskiy
2011-02-25 16:12   ` Johns Daniel
2011-02-25 16:27     ` Artem Bityutskiy [this message]
2011-02-25 17:11       ` Johns Daniel
2011-02-28 13:46         ` Artem Bityutskiy

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=1298651278.2346.2.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=johns.daniel@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.