linux.git/include/linux/dcache.h, branch v3.11-rc4

vfs: constify dentry parameter in d_count()

2013-07-20T01:06:27+00:00

so that it can be used in places like d_compare/d_hash
without causing a compiler warning.

Signed-off-by: Peng Tao 
Signed-off-by: Al Viro

helper for reading ->d_count

2013-07-05T14:59:33+00:00

Signed-off-by: Al Viro

Don't pass inode to ->d_hash() and ->d_compare()

2013-06-29T08:57:36+00:00

Instances either don't look at it at all (the majority of cases) or
only want it to find the superblock (which can be had as dentry->d_sb).
A few cases that want more are actually safe with dentry->d_inode -
the only precaution needed is the check that it hadn't been replaced with
NULL by rmdir() or by overwriting rename(), which case should be simply
treated as cache miss.

Signed-off-by: Linus Torvalds 
Signed-off-by: Al Viro

[O_TMPFILE] it's still short a few helpers, but infrastructure should be OK now...

2013-06-29T08:57:10+00:00

Signed-off-by: Al Viro

vfs: kill FS_REVAL_DOT by adding a d_weak_revalidate dentry op

2013-02-26T07:46:09+00:00

The following set of operations on a NFS client and server will cause

    server# mkdir a
    client# cd a
    server# mv a a.bak
    client# sleep 30  # (or whatever the dir attrcache timeout is)
    client# stat .
    stat: cannot stat `.': Stale NFS file handle

Obviously, we should not be getting an ESTALE error back there since the
inode still exists on the server. The problem is that the lookup code
will call d_revalidate on the dentry that "." refers to, because NFS has
FS_REVAL_DOT set.

nfs_lookup_revalidate will see that the parent directory has changed and
will try to reverify the dentry by redoing a LOOKUP. That of course
fails, so the lookup code returns ESTALE.

The problem here is that d_revalidate is really a bad fit for this case.
What we really want to know at this point is whether the inode is still
good or not, but we don't really care what name it goes by or whether
the dcache is still valid.

Add a new d_op->d_weak_revalidate operation and have complete_walk call
that instead of d_revalidate. The intent there is to allow for a
"weaker" d_revalidate that just checks to see whether the inode is still
good. This is also gives us an opportunity to kill off the FS_REVAL_DOT
special casing.

[AV: changed method name, added note in porting, fixed confusion re
having it possibly called from RCU mode (it won't be)]

Cc: NeilBrown 
Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

constify d_lookup() arguments

2013-02-23T04:31:35+00:00

Signed-off-by: Al Viro

constify __d_lookup() arguments

2013-02-23T04:31:35+00:00

Signed-off-by: Al Viro

vfs: remove d_path_with_unreachable

2013-02-23T04:31:33+00:00

The last caller was removed >2 years ago in commit 7b2a69ba7.

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: remove DCACHE_NEED_LOOKUP

2012-12-20T18:57:36+00:00

The code that relied on that flag was ripped out of btrfs quite some
time ago, and never added back. Josef indicated that he was going to
take a different approach to the problem in btrfs, and that we
could just eliminate this flag.

Cc: Josef Bacik 
Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: dcache: use DCACHE_DENTRY_KILLED instead of DCACHE_DISCONNECTED in d_kill()

2012-09-18T18:23:51+00:00

IBM reported a soft lockup after applying the fix for the rename_lock
deadlock.  Commit c83ce989cb5f ("VFS: Fix the nfs sillyrename regression
in kernel 2.6.38") was found to be the culprit.

The nfs sillyrename fix used DCACHE_DISCONNECTED to indicate that the
dentry was killed.  This flag can be set on non-killed dentries too,
which results in infinite retries when trying to traverse the dentry
tree.

This patch introduces a separate flag: DCACHE_DENTRY_KILLED, which is
only set in d_kill() and makes try_to_ascend() test only this flag.

IBM reported successful test results with this patch.

Signed-off-by: Miklos Szeredi 
Cc: Trond Myklebust 
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds