NFSv4: Update of VFS byte range lock must be atomic with the stateid update
authorTrond Myklebust <trond.myklebust@primarydata.com>
Sat, 24 Jan 2015 21:03:52 +0000 (16:03 -0500)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Sat, 24 Jan 2015 23:46:47 +0000 (18:46 -0500)
commitc69899a17ca4836230720e65493942d9582a0424
tree71d512aef12f51603adce636bfe0412ceda450e9
parent425c1d4e5b6d4bd700eb94ad8318bdb05431fdc7
NFSv4: Update of VFS byte range lock must be atomic with the stateid update

Ensure that we test the lock stateid remained unchanged while we were
updating the VFS tracking of the byte range lock. Have the process
replay the lock to the server if we detect that was not the case.

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4proc.c
include/linux/nfs_xdr.h