From: dwmw2@infradead.org (David Woodhouse)
To: linux-mtd@lists.infradead.org
Subject: Memory leak
Date: 11 Mar 2003 17:50:09 +0000 [thread overview]
Message-ID: <1047405009.24808.254.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <000e01c2e65b$71ca7020$210486da@ybb>
On Sun, 2003-03-09 at 16:46, matsunaga wrote:
> I am testing on NAND flash.
> There seems memory leak when you mount and unmount a device with some data.
> Dnode resource acquired during mount seems not to be freed during unmount.
Mea Culpa. It was introduced with the latest round of GC/crc changes. It
should be fixed in CVS now.
--
dwmw2
next prev parent reply other threads:[~2003-03-11 17:50 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
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 [this message]
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=1047405009.24808.254.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--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.