NFSv4: enhance nfs4_copy_lock_stateid to use a flock stateid if there is one
authorNeilBrown <neilb@suse.com>
Thu, 13 Oct 2016 04:26:47 +0000 (15:26 +1100)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Thu, 1 Dec 2016 22:58:05 +0000 (17:58 -0500)
commit8d42443166a5d3800756db98498a4961a5ea5de7
tree3d459d16bb6b022075a5819dba3629dca0b8cac0
parent1739347549653dc2463d208d7039f5e97b8f1e8b
NFSv4: enhance nfs4_copy_lock_stateid to use a flock stateid if there is one

A process can have two possible lock owner for a given open file:
a per-process Posix lock owner and a per-open-file flock owner
Use both of these when searching for a suitable stateid to use.

With this patch, READ/WRITE requests will use the correct stateid
if a flock lock is active.

Signed-off-by: NeilBrown <neilb@suse.com>
Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4state.c