summaryrefslogtreecommitdiffstats
path: root/fs/ext3/super.c
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@primarydata.com>2015-08-30 18:37:59 -0700
committerTrond Myklebust <trond.myklebust@primarydata.com>2015-08-30 18:45:04 -0700
commit4a1e2feb9d246775dee0f78ed5b18826bae2b1c5 (patch)
treecdba7acff417d6d01bc9830203b64304b5eebf24 /fs/ext3/super.c
parent90816d1ddacfb5a8b783f67e2c1a1bc77dc50ff4 (diff)
downloadop-kernel-dev-4a1e2feb9d246775dee0f78ed5b18826bae2b1c5.zip
op-kernel-dev-4a1e2feb9d246775dee0f78ed5b18826bae2b1c5.tar.gz
NFSv4.1: Fix a protocol issue with CLOSE stateids
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. Cc: stable@vger.kernel.org # v4.0+ Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/ext3/super.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud