| commit | ad1a2c878ca70829874b4fcc83223cccb4e26dab | |
| author | J. Bruce Fields <bfields@redhat.com> | |
| Thu, 14 Jul 2011 20:50:36 +0000 (14 20:50 +0000) | ||
| committer | Alex Elder <aelder@sgi.com> | |
| Wed, 20 Jul 2011 23:35:21 +0000 (20 18:35 -0500) | ||
| tree | fe664063bf7675a1be90c8c61c5ec7e09f99300e | treesnapshot (tar.gz zip) |
| parent | adab0f67d1cdaf468bbc311bce4d61f17626a536 | commitdiff |
xfs: failure mapping nfs fh to inode should return ESTALE
On xfs exports, nfsd is incorrectly returning ENOENT instead of
ESTALE on attempts to use a filehandle of a deleted file (spotted
with pynfs test PUTFH3). The ENOENT was coming from xfs_iget.
(It's tempting to wonder whether we should just map all xfs_iget
errors to ESTALE, but I don't believe so--xfs_iget can also return
ENOMEM at least, which we wouldn't want mapped to ESTALE.)
While we're at it, the other return of ENOENT in xfs_nfs_get_inode()
also looks wrong.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Alex Elder <aelder@sgi.com>
On xfs exports, nfsd is incorrectly returning ENOENT instead of
ESTALE on attempts to use a filehandle of a deleted file (spotted
with pynfs test PUTFH3). The ENOENT was coming from xfs_iget.
(It's tempting to wonder whether we should just map all xfs_iget
errors to ESTALE, but I don't believe so--xfs_iget can also return
ENOMEM at least, which we wouldn't want mapped to ESTALE.)
While we're at it, the other return of ENOENT in xfs_nfs_get_inode()
also looks wrong.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Alex Elder <aelder@sgi.com>
| fs/xfs/linux-2.6/xfs_export.c | diffblobblamehistory |