summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/lists.py
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2025-01-27 00:50:19 +0300
committerChuck Lever <chuck.lever@oracle.com>2025-03-10 16:10:57 +0300
commit3b60984e79fcb040509f09464406ed1bc6fed6a0 (patch)
tree4bdb3f09e851ba83f57f535140aa6d64170d3bbf /scripts/gdb/linux/lists.py
parent370345b4bd184a49ac68d6591801e5e3605b355a (diff)
downloadlinux-3b60984e79fcb040509f09464406ed1bc6fed6a0.tar.xz
NFSD: Return NFS4ERR_FILE_OPEN only when renaming over an open file
RFC 8881 Section 18.26.4 paragraphs 1 - 3 tell us that RENAME should return NFS4ERR_FILE_OPEN only when the target object is a file that is currently open. If the target is a directory, some other status must be returned. Generally I expect that a delegation recall will be triggered in some of these circumstances. In other cases, the VFS might return -EBUSY for other reasons, and NFSD has to ensure that errno does not leak to clients as a status code that is not permitted by spec. There are some error flows where the target dentry hasn't been found yet. The default value for @type therefore is S_IFDIR to return an alternate status code in those cases. Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'scripts/gdb/linux/lists.py')
0 files changed, 0 insertions, 0 deletions