summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_error.h
diff options
context:
space:
mode:
authorMenyhart Zoltan <Zoltan.Menyhart@bull.net>2010-09-12 19:55:26 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2010-09-12 19:55:26 -0400
commitfbf3fdd2443965d9ba6fb4b5fecd1f6e0847218f (patch)
tree55e1b68c3304b35e8c7e8d1f0de54521189908b9 /fs/xfs/xfs_error.h
parentb20d37ca9561711c6a3c4b859c2855f49565e061 (diff)
downloadop-kernel-dev-fbf3fdd2443965d9ba6fb4b5fecd1f6e0847218f.zip
op-kernel-dev-fbf3fdd2443965d9ba6fb4b5fecd1f6e0847218f.tar.gz
statfs() gives ESTALE error
Hi, An NFS client executes a statfs("file", &buff) call. "file" exists / existed, the client has read / written it, but it has already closed it. user_path(pathname, &path) looks up "file" successfully in the directory-cache and restarts the aging timer of the directory-entry. Even if "file" has already been removed from the server, because the lookupcache=positive option I use, keeps the entries valid for a while. nfs_statfs() returns ESTALE if "file" has already been removed from the server. If the user application repeats the statfs("file", &buff) call, we are stuck: "file" remains young forever in the directory-cache. Signed-off-by: Zoltan Menyhart <Zoltan.Menyhart@bull.net> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Cc: stable@kernel.org
Diffstat (limited to 'fs/xfs/xfs_error.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud