[PATCH 0/1 v2][SRU][focal:linux] NFSv4.1: Don't rebind to the same source port when reconnecting to the server
Stefan Bader
stefan.bader at canonical.com
Thu Dec 1 09:14:45 UTC 2022
On 28.11.22 15:43, Tim Gardner wrote:
> BugLink: https://bugs.launchpad.net/bugs/1997488
>
> SRU Justification
>
> Microsoft asked for this backport complaining that,
> "NFS 4.1 mounts on AKS are reusing the same source port when a reconnect needs to happen".
>
> This issue looks applicable to the generic kernel, though I'd be happy to only apply
> to Azure if the risk is deemed too high.
>
> [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
>
>
Instead of references what is missing (SHA1) it would find it more helpful to
outline what kind of adaptions had to be made.
Also, has there been testing to verify the backport was ok?
-Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20221201/35ad9816/attachment-0001.sig>
More information about the kernel-team
mailing list