diff options
| author | Trond Myklebust <[email protected]> | 2012-05-25 15:00:06 -0400 |
|---|---|---|
| committer | Trond Myklebust <[email protected]> | 2012-05-25 16:17:42 -0400 |
| commit | 89a217360ef4e96eb83758cb9647f1c42581b097 (patch) | |
| tree | a802dbd6fdca71da10b7f5983215f83a4fadeb2b /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | be0bfed002e0c64a91dacc42a4dab6e883e6bc7e (diff) | |
NFSv4.1: Handle NFS4ERR_SEQ_MISORDERED when confirming the lease
Apparently the patch "NFS: Always use the same SETCLIENTID boot verifier"
is tickling a Linux nfs server bug, and causing a regression: the server
can get into a situation where it keeps replying NFS4ERR_SEQ_MISORDERED
to our CREATE_SESSION request even when we are sending the correct
sequence ID.
Fix this by purging the lease and then retrying.
Reported-by: Bryan Schumaker <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions