diff options
author | Trond Myklebust <trond.myklebust@primarydata.com> | 2016-06-25 19:19:28 -0400 |
---|---|---|
committer | Sasha Levin <sasha.levin@oracle.com> | 2016-07-12 08:47:17 -0400 |
commit | 35bec11905351b40951cace13e568e69a6678475 (patch) | |
tree | e27f88d51c0331dbe783eee44da101449dcb9c8d /include | |
parent | 129786640b730ca8f1e0d9d221470701ddd32dd4 (diff) | |
download | linux-stable-35bec11905351b40951cace13e568e69a6678475.tar.gz linux-stable-35bec11905351b40951cace13e568e69a6678475.tar.bz2 linux-stable-35bec11905351b40951cace13e568e69a6678475.zip |
NFS: Fix another OPEN_DOWNGRADE bug
[ Upstream commit e547f2628327fec6afd2e03b46f113f614cca05b ]
Olga Kornievskaia reports that the following test fails to trigger
an OPEN_DOWNGRADE on the wire, and only triggers the final CLOSE.
fd0 = open(foo, RDRW) -- should be open on the wire for "both"
fd1 = open(foo, RDONLY) -- should be open on the wire for "read"
close(fd0) -- should trigger an open_downgrade
read(fd1)
close(fd1)
The issue is that we're missing a check for whether or not the current
state transitioned from an O_RDWR state as opposed to having transitioned
from a combination of O_RDONLY and O_WRONLY.
Reported-by: Olga Kornievskaia <aglo@umich.edu>
Fixes: cd9288ffaea4 ("NFSv4: Fix another bug in the close/open_downgrade code")
Cc: stable@vger.kernel.org # 2.6.33+
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions