From: Steve Lord <lord@xfs.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: negative dentry_stat.nr_unused causes aggressive dcache pruning
Date: Wed, 08 Dec 2004 16:16:52 -0600 [thread overview]
Message-ID: <41B77D54.4080909@xfs.org> (raw)
I have seen this stat go negative (just from booting up a multi cpu box),
and looking at the code, it is manipulated without locking in a number
of places. I have only seen this in real life on a 2.4 kernel, but 2.6
also looks vulnerable.
In 2.4 this can cause shrink_dcache_memory to attempt to push the whole
dcache out by calling prune_dcache with a negative parameter, prune_dcache
just keeps going until count hits zero or the dentry_unused list
empties.
In 2.6 kernels I do not see a real use of the variable which would cause harm,
although is someone was to start relying on more than -1 coming back from
shrink_dcache_memory there might be problems.
The problem code is dput which is the only place it is manipulated
without the dcache lock.
nr_dentry is not mp safe either, but no one depends on that.
Steve
next reply other threads:[~2004-12-08 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 22:16 Steve Lord [this message]
2004-12-08 23:01 ` negative dentry_stat.nr_unused causes aggressive dcache pruning Greg Banks
2004-12-09 10:09 ` Andrew Morton
2004-12-09 16:33 ` Steve Lord
2004-12-09 20:54 ` Steve Lord
2004-12-09 21:19 ` Andrew Morton
2004-12-09 21:51 ` Steve Lord
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=41B77D54.4080909@xfs.org \
--to=lord@xfs.org \
--cc=linux-kernel@vger.kernel.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.