From: Artem Bityutskiy <dedekind@infradead.org>
To: John.Smith@pace.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI memory leak after creating and removing volumes
Date: Tue, 17 Feb 2009 14:23:57 +0200 [thread overview]
Message-ID: <1234873437.17790.265.camel@localhost.localdomain> (raw)
In-Reply-To: <F21E92E7B38A1F4D9211341290F7569807EED1AE@salexc1.pace.internal>
On Tue, 2009-02-17 at 12:01 +0000, John.Smith@pace.com wrote:
> Hello,
> I am using a 2.6.18 Kernel, patched with MTD from Kernel 2.6.21, and
> UBI from the mainline kernel a few days later on 1 May 2007. The
> whole is running on an embedded MIPS device.
>
> I have NAND, and UBI, and gluebi, and jffs2. I use jffs2, mounted on
> an mtdblock device. Broadly, it all works.
>
> I am experiencing a memory leak revealed in recent stress tests. The
> stress tests create and delete many UBI volumes, and are are broadly
> equivelent to the following:
Can you please enable /proc/slab_allocators - it tracks all allocators
and if we have a leak - it may point to the function which is guilty.
To have /proc/slab_allocators, do the following:
1. Enable SLAB, not SLUB. In kernel config menu got to
"General setup --->", then
"Choose SLAB allocator (SLUB (Unqueued Allocator)) --->"
and choose SLAB.
2. Go to the root menu, then go to
"Kernel hacking --->" and enable
"[*] Debug slab memory allocations" and
"[*] Memory leak debugging"
Recompile the kernel, and you will have a nice instrumentation to find
memory leak - the /proc/slab_allocators file. Please, play with this.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-02-17 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 12:01 UBI memory leak after creating and removing volumes John.Smith
2009-02-17 12:23 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 14:33 John.Smith
2009-02-17 15:24 ` Artem Bityutskiy
2009-02-17 15:24 ` Artem Bityutskiy
2009-02-17 22:02 ` John Smith
2009-02-17 15:39 ` Artem Bityutskiy
2009-02-21 21:30 ` John Smith
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=1234873437.17790.265.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=John.Smith@pace.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