From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: Memory leak
Date: Mon, 10 Mar 2003 15:53:09 +0100 [thread overview]
Message-ID: <200303101553.09156.tglx@linutronix.de> (raw)
In-Reply-To: <000f01c2e691$1a319a60$210486da@ybb>
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.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de
next prev parent reply other threads:[~2003-03-10 14:53 UTC|newest]
Thread overview: 29+ 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 [this message]
2003-03-10 14:14 ` David Woodhouse
2003-03-10 15:48 ` matsunaga
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 --
2026-01-19 5:14 [PATCH v26 2/2] status: add status.compareBranches config for multiple branch comparisons Jeff King
2026-01-20 9:49 ` Memory leak Harald Nordgren
2026-01-20 13:22 ` Harald Nordgren
2026-01-20 21:42 ` Junio C Hamano
2026-01-21 18:47 ` Junio C Hamano
2026-01-21 20:49 ` Jeff King
2026-01-22 15:03 ` Harald Nordgren
2026-01-22 18:19 ` Junio C Hamano
2008-04-09 13:54 hinko.kocevar
2003-03-12 19:50 Memory Leak Aman
2003-03-12 20:29 ` Matt Porter
2002-06-20 15:06 Memory leak diekema_jon
2002-06-20 7:52 Skip Gaede
2002-06-22 2:22 ` Skip Gaede
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=200303101553.09156.tglx@linutronix.de \
--to=tglx@linutronix.de \
--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.