diff options
| author | Nick Piggin <npiggin@kernel.dk> | 2011-01-07 06:49:23 (GMT) |
|---|---|---|
| committer | Nick Piggin <npiggin@kernel.dk> | 2011-01-07 06:50:18 (GMT) |
| commit | fe15ce446beb3a33583af81ffe6c9d01a75314ed (patch) | |
| tree | bc8af66b6dd2d0f21a2a3f48a19975ae2cdbae4e /fs/proc/generic.c | |
| parent | 5eef7fa905c814826f518aca2d414ca77508ce30 (diff) | |
| download | linux-fe15ce446beb3a33583af81ffe6c9d01a75314ed.tar.xz | |
fs: change d_delete semantics
Change d_delete from a dentry deletion notification to a dentry caching
advise, more like ->drop_inode. Require it to be constant and idempotent,
and not take d_lock. This is how all existing filesystems use the callback
anyway.
This makes fine grained dentry locking of dput and dentry lru scanning
much simpler.
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Diffstat (limited to 'fs/proc/generic.c')
| -rw-r--r-- | fs/proc/generic.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/proc/generic.c b/fs/proc/generic.c index dd29f03..1d607be 100644 --- a/fs/proc/generic.c +++ b/fs/proc/generic.c @@ -400,7 +400,7 @@ static const struct inode_operations proc_link_inode_operations = { * smarter: we could keep a "volatile" flag in the * inode to indicate which ones to keep. */ -static int proc_delete_dentry(struct dentry * dentry) +static int proc_delete_dentry(const struct dentry * dentry) { return 1; } |