From: matsunaga_kazuhisa@yahoo.co.jp (matsunaga)
To: linux-mtd@lists.infradead.org
Subject: Memory leak
Date: Tue, 11 Mar 2003 00:48:22 +0900 [thread overview]
Message-ID: <002601c2e71c$7abe7d40$210486da@ybb> (raw)
In-Reply-To: 1047305682.23941.44.camel@passion.cambridge.redhat.com
Hi
> On Mon, 2003-03-10 at 14:53, Thomas Gleixner wrote:
> > On Monday 10 March 2003 00:10, matsunaga wrote:
> > > Yes, I use JFFS2.
> > > If you mount a device with a file on JFFS2, a dirent node and a dnode are
> > > alloced. But upper layer does not issue, jffs2_clear_inode for an inode of
> > > the dnode during unmount. You can see it just by free command if my
> > > implementation is not wrong.
> > on umount put_super is called
> > void jffs2_put_super (struct super_block *sb)
> > {
> > SNIP
> > jffs2_free_ino_caches(c);
> > jffs2_free_raw_node_refs(c);
> > vfree(c->blocks);
> > SNIP
> > }
> > So everything is freed there. Are you looking at the first line of output from
> > free (Mem:) ? Have a look at the second line (-/+ buffers/cache). If this is
> > worrying you too, then send output of free before mount and after umount.
>
> If you can rmmod jffs2 without a BUG() then it's freed everything in its
> own slabs, although it is theoretically possible that it's leaked
> something kmalloc'd. Unlikely though.
It is correct that rmmod will resolve it, but my concern is a consistency of resource and memory saving.
Dnode resource acuqired during mount seems not to be refereneced when you access to the file.
Best regards.
__________________________________________________
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
next prev parent reply other threads:[~2003-03-10 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 16:46 Memory leak matsunaga
2003-03-09 17:37 ` Charles Manning
2003-03-09 19:10 ` Thomas Gleixner
2003-03-09 23:10 ` matsunaga
2003-03-10 14:53 ` Thomas Gleixner
2003-03-10 14:14 ` David Woodhouse
2003-03-10 15:48 ` matsunaga [this message]
2003-03-10 16:02 ` David Woodhouse
2003-03-10 16:26 ` matsunaga
2003-03-10 17:04 ` David Woodhouse
2003-03-11 15:52 ` matsunaga
2003-03-11 18:39 ` Thomas Gleixner
2003-03-10 15:36 ` matsunaga
2003-03-11 17:50 ` David Woodhouse
2003-03-12 15:47 ` dnode of meta data matsunaga
2003-03-13 7:14 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2008-04-09 13:54 Memory leak hinko.kocevar
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='002601c2e71c$7abe7d40$210486da@ybb' \
--to=matsunaga_kazuhisa@yahoo.co.jp \
--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