From: David Woodhouse <dwmw2@infradead.org>
To: Frederic Giasson <fgiasson@mediatrix.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Memory leak problem with JFFS2
Date: Wed, 31 Jul 2002 19:04:35 +0100 [thread overview]
Message-ID: <25738.1028138675@redhat.com> (raw)
In-Reply-To: <2702075D4DE2B043BF5EB82E9CFAD45B0BD37B@mail1.mediatrix.com>
fgiasson@mediatrix.com said:
> You have the right procedure to reproduce the problem ( vmstat ; while
> true ; do mount -t jffs2 mtd0 /mnt/spare ; ). I can reproduce the
> problem using this line on my system.
> I updated my JFFS2 code with the lastest from CVS, and I am using
> kernel 2.4.19-rc2, and the problem is still there. Do you think you
> could do the same test under 2.4.19-rc2?
I'll have a go. This happens in the CVS code, not the jffs2-2_4-branch
code, right?
--
dwmw2
next prev parent reply other threads:[~2002-07-31 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 16:14 Memory leak problem with JFFS2 Frederic Giasson
2002-07-31 18:04 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 18:18 Frederic Giasson
2002-07-31 14:48 Frederic Giasson
2002-07-31 15:17 ` David Woodhouse
2002-07-03 13:38 Frederic Giasson
2002-07-10 9:47 ` David Woodhouse
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=25738.1028138675@redhat.com \
--to=dwmw2@infradead.org \
--cc=fgiasson@mediatrix.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