aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@primarydata.com>2015-01-24 18:38:15 -0500
committerTrond Myklebust <trond.myklebust@primarydata.com>2015-01-24 18:46:46 -0500
commit6b447539aa9aaac0a0215f3e28a0839553210e7e (patch)
tree66bfecb6aecbf164a9ab61dcb5ebe639c4d6d43f /tools/perf/scripts/python/call-graph-from-postgresql.py
parentNFSv4: Fix atomicity problems with lock stateid updates (diff)
downloadwireguard-linux-6b447539aa9aaac0a0215f3e28a0839553210e7e.tar.xz
wireguard-linux-6b447539aa9aaac0a0215f3e28a0839553210e7e.zip
NFSv4: Always do open_to_lock_owner if the lock stateid is uninitialised
The original text in RFC3530 was terribly confusing since it conflated lockowners and lock stateids. RFC3530bis clarifies that you must use open_to_lock_owner when there is no lock state for that file+lockowner combination. 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