projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 39c6daa) | patch
NFSv4.1: Select the "most recent locking state" for read/write/setattr stateids
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Sun, 17 Mar 2013 19:31:15 +0000 (15:31 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Mon, 25 Mar 2013 16:04:11 +0000 (12:04 -0400)
commit3b66486c4c7136f8d4bbe1306d581fadc6bce4c7
tree953049d16122695bab4388ae86394bb2d09bb236tree | snapshot
parent39c6daae70fe7692fc2d28738c7ebd63f0318741commit | diff
NFSv4.1: Select the "most recent locking state" for read/write/setattr stateids

Follow the practice described in section 8.2.2 of RFC5661: When sending a
read/write or setattr stateid, set the seqid field to zero in order to
signal that the NFS server should apply the most recent locking state.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4proc.c diff | blob | blame | history
fs/nfs/nfs4state.c diff | blob | blame | history
include/linux/nfs_fs_sb.h diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)