NFSv4.1: Select the "most recent locking state" for read/write/setattr stateids

Browse source

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>

...

This commit is contained in:

Trond Myklebust 2013-03-17 15:31:15 -04:00

parent 39c6daae70

commit 3b66486c4c

3 changed files with 5 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

fs/nfs/nfs4proc.c

View file

2

fs/nfs/nfs4state.c

View file

1

include/linux/nfs_fs_sb.h

View file