LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: rsc@swtch.com
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix quadratic behavior of shrink_dcache_parent()
Date: Sat, 10 Feb 2007 09:46:28 +0100 [thread overview]
Message-ID: <E1HFnsK-0007Ep-00@dorka.pomaz.szeredi.hu> (raw)
In-Reply-To: <ee9e417a0702091623t1ccf55b8wb05b64b9c51474a6@mail.gmail.com> (rsc@swtch.com)
> > "The file system mounted on /tmp/z in the example contains 2^50
> > directories". heh.
> >
> > I do wonder how realistic this problem is in real life.
>
> That's a fair concern, although I was trying this as part
> of evaluating how much someone could hose a system
> if we let them mount arbitrary FUSE servers. And the
> answer is: they could make it completely unusable,
> requiring reboot.
>
> I ran a later test that printed how deep it got into
> the file tree and it was only a few hundred thousand
> if I recall correctly. A determined attacker might even
> manage to do this in a normal file system.
Unfortunately this patch doesn't completely solve this problem, since
the system will still be hosed due to all memory being used up by
dentries. And I bet the OOM killer won't find the real target (du)
but will kill anything before that.
So the second part of the problem is to somehow limit the number of
dentries used. Not easy...
Miklos
next prev parent reply other threads:[~2007-02-10 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 22:01 [PATCH] fix quadratic behavior of shrink_dcache_parent() Miklos Szeredi
2007-02-10 0:00 ` Andrew Morton
2007-02-10 0:23 ` Russ Cox
2007-02-10 0:40 ` Andrew Morton
2007-02-10 8:46 ` Miklos Szeredi [this message]
2007-02-10 10:51 ` Andi Kleen
2007-02-10 12:57 ` Russ Cox
2007-02-11 12:13 ` Miklos Szeredi
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=E1HFnsK-0007Ep-00@dorka.pomaz.szeredi.hu \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rsc@swtch.com \
/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;
as well as URLs for NNTP newsgroup(s).