diff options
| author | Trond Myklebust <trond.myklebust@primarydata.com> | 2015-08-30 18:37:59 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2015-09-29 19:26:10 +0200 |
| commit | 3d5c6b90ed90eadcd9c66951877697d848e63ac1 (patch) | |
| tree | 931bd7e05cf8c5c5e3933809e076b989c953a905 /drivers/scsi/mpt2sas/mpi/mpi2_raid.h | |
| parent | f6384199b2592674c7e6cfcfb4c0c54eacf992d7 (diff) | |
NFSv4.1: Fix a protocol issue with CLOSE stateids
commit 4a1e2feb9d246775dee0f78ed5b18826bae2b1c5 upstream.
According to RFC5661 Section 18.2.4, CLOSE is supposed to return
the zero stateid. This means that nfs_clear_open_stateid_locked()
cannot assume that the result stateid will always match the 'other'
field of the existing open stateid when trying to determine a race
with a parallel OPEN.
Instead, we look at the argument, and check for matches.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/scsi/mpt2sas/mpi/mpi2_raid.h')
0 files changed, 0 insertions, 0 deletions