NFS 4.1 mounts on AKS are reusing the same source port when a reconnect needs to happen
Bug #1997488 reported by
Tim Gardner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
In Progress
|
Medium
|
Tim Gardner | ||
Bug Description
SRU Justification
[Impact]
NFSv2, v3 and NFSv4 servers often have duplicate replay caches that look
at the source port when deciding whether or not an RPC call is a replay
of a previous call. This requires clients to perform strange TCP gymnastics
in order to ensure that when they reconnect to the server, they bind
to the same source port.
NFSv4.1 and NFSv4.2 have sessions that provide proper replay semantics,
that do not look at the source port of the connection. This patch therefore
ensures they can ignore the rebind requirement.
[Where things could go wrong]
NFS reconnects may erroneously fail.
[Other Info]
SF: #00345839
Revision history for this message
| Tim Gardner (timg-tpi) wrote | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Fix Released |
| Changed in linux (Ubuntu Focal): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
To post a comment you must log in.
Fix patch: commit e6237b6feb37582