From: Andrew Morton <akpm@osdl.org>
To: Jan Blunck <jblunck@suse.de>
Cc: viro@zeniv.linux.org.uk, dev@sw.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shrink_dcache_parent() races against shrink_dcache_memory()
Date: Sun, 22 Jan 2006 21:22:43 -0800 [thread overview]
Message-ID: <20060122212243.20ce26c5.akpm@osdl.org> (raw)
In-Reply-To: <20060120203645.GF24401@hasse.suse.de>
Jan Blunck <jblunck@suse.de> wrote:
>
> Kirill Korotaev <dev@sw.ru> discovered a race between shrink_dcache_parent()
> and shrink_dcache_memory(). That one is based on dput() is calling
> dentry_iput() too early and therefore is giving up the dcache_lock. This leads
> to the situation that the parent dentry might be still referenced although all
> childs are already dead. This parent is ignore by a concurrent select_parent()
> call which might be the reason for busy inode after umount failures.
>
> This is from Kirill's original patch:
>
> CPU 1 CPU 2
> ~~~~~ ~~~~~
> umount /dev/sda1
> generic_shutdown_super shrink_dcache_memory
> shrink_dcache_parent prune_one_dentry
> select_parent dput <<<< child is dead, locks are released,
> but parent is still referenced!!! >>>>
> skip dentry->parent,
> since it's d_count > 0
>
> message: BUSY inodes after umount...
> <<< parent is left on dentry_unused list,
> referencing freed super block >>>
>
> This patch is introducing dput_locked() which is doing all the dput work
> except of freeing up the dentry's inode and memory itself. Therefore, when the
> dcache_lock is given up, all the reference counts of the parents are correct.
> prune_one_dentry() must also use the dput_locked version and free up the
> inodes and the memory of the parents later. Otherwise we have an incorrect
> reference count on the parents of the dentry to prune.
>
> ...
> -void dput(struct dentry *dentry)
> +static void dput_locked(struct dentry *dentry, struct list_head *list)
> {
> if (!dentry)
> return;
>
> -repeat:
> - if (atomic_read(&dentry->d_count) == 1)
> - might_sleep();
> - if (!atomic_dec_and_lock(&dentry->d_count, &dcache_lock))
> + if (!atomic_dec_and_test(&dentry->d_count))
> return;
>
> +
>
> ...
>
> +void dput(struct dentry *dentry)
> +{
> + LIST_HEAD(free_list);
> +
> + if (!dentry)
> + return;
> +
> + if (atomic_add_unless(&dentry->d_count, -1, 1))
> + return;
> +
> + spin_lock(&dcache_lock);
> + dput_locked(dentry, &free_list);
> + spin_unlock(&dcache_lock);
This seems to be an open-coded copy of atomic_dec_and_lock()?
next prev parent reply other threads:[~2006-01-23 5:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 20:36 Jan Blunck
2006-01-23 5:22 ` Andrew Morton [this message]
2006-01-23 8:12 ` Kirill Korotaev
2006-01-23 15:13 ` Jan Blunck
2006-01-23 8:07 ` Kirill Korotaev
2006-01-23 15:57 ` Jan Blunck
2006-01-24 5:54 ` Balbir Singh
2006-01-24 9:48 ` Kirill Korotaev
2006-01-24 11:10 ` Balbir Singh
2006-01-24 17:18 ` Kirill Korotaev
2006-01-25 7:03 ` Balbir Singh
2006-01-30 12:03 ` Jan Blunck
2006-01-30 14:38 ` Balbir Singh
2006-01-30 14:54 ` Jan Blunck
2006-01-30 15:02 ` Kirill Korotaev
2006-01-30 15:25 ` Jan Blunck
2006-01-30 15:31 ` Kirill Korotaev
2006-01-30 14:42 ` Kirill Korotaev
2006-01-30 14:58 ` Jan Blunck
2006-01-30 15:59 ` Kirill Korotaev
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=20060122212243.20ce26c5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome