diff options
| author | Trond Myklebust | 2016-07-24 17:46:06 +0200 |
|---|---|---|
| committer | Trond Myklebust | 2016-07-24 22:16:38 +0200 |
| commit | ecebb80bf3ee8c5f3172f00bb17ba55f9e3ae24f (patch) | |
| tree | 32d5c42f2e3358342549f3991241a4ca253b2363 /drivers/iommu | |
| parent | pNFS: Always update the layout stateid if NFS_LAYOUT_INVALID_STID is set (diff) | |
| download | kernel-qcow2-linux-ecebb80bf3ee8c5f3172f00bb17ba55f9e3ae24f.tar.gz kernel-qcow2-linux-ecebb80bf3ee8c5f3172f00bb17ba55f9e3ae24f.tar.xz kernel-qcow2-linux-ecebb80bf3ee8c5f3172f00bb17ba55f9e3ae24f.zip | |
pNFS: Always update the layout barrier seqid on LAYOUTGET
Currently, pnfs_set_layout_stateid() will update the layout sequence
id barrier only if the stateid itself is newer than the current
layout stateid. However in a situation where multiple LAYOUTGET calls
and a LAYOUTRETURN raced, it is entirely possible for one of the
LAYOUTGET to set the current stateid to something newer than the
LAYOUTRETURN that needs to set the barrier.
The fix is to allow the "update_barrier" flag to force a check as to
whether or not the barrier needs to be updated.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'drivers/iommu')
0 files changed, 0 insertions, 0 deletions