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 14:38:44 +0200 [thread overview]
Message-ID: <1298637524.2798.103.camel@localhost> (raw)
In-Reply-To: <AANLkTimN5eBifpcyfJYo9s51U+kEi1ZemFnOm7p2rcxQ@mail.gmail.com>
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.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-02-25 12:40 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 [this message]
2011-02-25 16:12 ` Johns Daniel
2011-02-25 16:27 ` Artem Bityutskiy
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=1298637524.2798.103.camel@localhost \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox