diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2014-05-30 11:25:30 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2014-10-09 02:38:59 -0400 |
commit | 29355c3904e1765948c7721719a028b7eb5dfe1d (patch) | |
tree | ed3b5660e0df3f0c725d678fa80d4cff719a29cd /crypto/asymmetric_keys | |
parent | bbd5192412fdedbae00888316bfe350bf89d0458 (diff) |
d_prune_alias(): just lock the parent and call __dentry_kill()
The only reason for games with ->d_prune() was __d_drop(), which
was needed only to force dput() into killing the sucker off.
Note that lock_parent() can be called under ->i_lock and won't
drop it, so dentry is safe from somebody managing to kill it
under us - it won't happen while we are holding ->i_lock.
__dentry_kill() is called only with ->d_lockref.count being 0
(here and when picked from shrink list) or 1 (dput() and dropping
the ancestors in shrink_dentry_list()), so it will never be called
twice - the first thing it's doing is making ->d_lockref.count
negative and once that happens, nothing will increment it.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'crypto/asymmetric_keys')
0 files changed, 0 insertions, 0 deletions