From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Burton Windle <bwindle@fint.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: fsstress causes memory leak in test6, test8
Date: Mon, 27 Oct 2003 12:16:09 +0000 [thread overview]
Message-ID: <20031027121609.GA27611@redhat.com> (raw)
In-Reply-To: <20031026170241.628069e3.akpm@osdl.org>
On Sun, Oct 26, 2003 at 05:02:41PM -0800, Andrew Morton wrote:
> It is not a "leak" as such - the dentries will get shrunk in normal usage
> (create enough non-dir dentries and the "leaked" directory dentries will
> get reclaimed). The really deep directories which fsstress creates
> demonstrated the bug.
This could explain the random reiserfs oopses/hangs I was seeing several
months back after running fsstress for a day or so. The reiser folks
were scratching their heads, and we even put it down to flaky hardware
or maybe even a CPU bug back then.
> Given that it took a year for anyone to notice, it's probably best that
> this not be included for 2.6.0.
I agree in a "lets get 2.6 out the door" sense, but once thats 'out
there' a user-level DoS should be fixed up pretty quickly.
The paranoid could always run 2.6-mm I guess 8-)
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-10-27 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0310251842570.371@morpheus>
2003-10-27 1:02 ` fsstress causes memory leak in test6, test8 Andrew Morton
2003-10-27 1:10 ` Linus Torvalds
2003-10-27 12:16 ` Dave Jones [this message]
2003-10-27 12:31 ` Hans Reiser
2003-10-27 12:36 ` Dave Jones
2003-10-27 12:47 ` Nikita Danilov
2003-10-27 13:19 ` Hans Reiser
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=20031027121609.GA27611@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=bwindle@fint.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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