diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2009-11-11 16:15:42 +0900 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2009-11-11 16:15:42 +0900 |
| commit | 96d25e532234bec1a1989e6e1baf702d43a78b0d (patch) | |
| tree | c299127355fbf90ca0a4b400c88022e952f013af /fs | |
| parent | 799dd75b1a8380a967c929a4551895788c374b31 (diff) | |
| download | kernel_samsung_tuna-96d25e532234bec1a1989e6e1baf702d43a78b0d.zip kernel_samsung_tuna-96d25e532234bec1a1989e6e1baf702d43a78b0d.tar.gz kernel_samsung_tuna-96d25e532234bec1a1989e6e1baf702d43a78b0d.tar.bz2 | |
NFSv4: Fix a cache validation bug which causes getcwd() to return ENOENT
Changeset a65318bf3afc93ce49227e849d213799b072c5fd (NFSv4: Simplify some
cache consistency post-op GETATTRs) incorrectly changed the getattr
bitmap for readdir().
This causes the readdir() function to fail to return a
fileid/inode number, which again exposed a bug in the NFS readdir code that
causes spurious ENOENT errors to appear in applications (see
http://bugzilla.kernel.org/show_bug.cgi?id=14541).
The immediate band aid is to revert the incorrect bitmap change, but more
long term, we should change the NFS readdir code to cope with the
fact that NFSv4 servers are not required to support fileids/inode numbers.
Reported-by: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: stable@kernel.org
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/nfs/nfs4proc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c index ff37454..741a562 100644 --- a/fs/nfs/nfs4proc.c +++ b/fs/nfs/nfs4proc.c @@ -2767,7 +2767,7 @@ static int _nfs4_proc_readdir(struct dentry *dentry, struct rpc_cred *cred, .pages = &page, .pgbase = 0, .count = count, - .bitmask = NFS_SERVER(dentry->d_inode)->cache_consistency_bitmask, + .bitmask = NFS_SERVER(dentry->d_inode)->attr_bitmask, }; struct nfs4_readdir_res res; struct rpc_message msg = { |