diff options
| author | Trond Myklebust <trond.myklebust@primarydata.com> | 2015-01-24 23:07:56 +0300 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2015-01-25 01:27:41 +0300 |
| commit | 39071e6fff7d7e11a5993afd67240ef04a4d05a0 (patch) | |
| tree | a5eb6dbf670233f04396262ce6f3ed370ec87d71 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 63f5f796af613898669b23ccfc091ec77de7591c (diff) | |
| download | linux-39071e6fff7d7e11a5993afd67240ef04a4d05a0.tar.xz | |
NFSv4: Fix atomicity problems with lock stateid updates
When we update the lock stateid, we really do need to ensure that this is
done under the state->state_lock, and that we are indeed only updating
confirmed locks with a newer version of the same stateid.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions