diff options
| author | Olga Kornievskaia <kolga@netapp.com> | 2018-10-04 14:45:00 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-25 15:54:43 +0100 |
| commit | f3ec47899154bd64ac393203a4b0e67691f9bc7f (patch) | |
| tree | 30ef963fecce352f8556e24927ab1f9f80f736e3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 0deab3d2d62d51aaa26971f641262d8e32c180a0 (diff) | |
NFSv4.x: fix lock recovery during delegation recall
[ Upstream commit 44f411c353bf6d98d5a34f8f1b8605d43b2e50b8 ]
Running "./nfstest_delegation --runtest recall26" uncovers that
client doesn't recover the lock when we have an appending open,
where the initial open got a write delegation.
Instead of checking for the passed in open context against
the file lock's open context. Check that the state is the same.
Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions