diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2019-06-11 17:01:16 +0200 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2019-06-19 22:40:40 +0200 |
commit | 1e091c3bbf51d34d5d96337a59ce5ab2ac3ba2cc (patch) | |
tree | 3a5a50ac864afc4b4cfeafb8738b8f6e5bb3341c /fs/nfsd | |
parent | Revert "lockd: Show pid of lockd for remote locks" (diff) | |
download | linux-1e091c3bbf51d34d5d96337a59ce5ab2ac3ba2cc.tar.xz linux-1e091c3bbf51d34d5d96337a59ce5ab2ac3ba2cc.zip |
svcrdma: Ignore source port when computing DRC hash
The DRC appears to be effectively empty after an RPC/RDMA transport
reconnect. The problem is that each connection uses a different
source port, which defeats the DRC hash.
Clients always have to disconnect before they send retransmissions
to reset the connection's credit accounting, thus every retransmit
on NFS/RDMA will miss the DRC.
An NFS/RDMA client's IP source port is meaningless for RDMA
transports. The transport layer typically sets the source port value
on the connection to a random ephemeral port. The server already
ignores it for the "secure port" check. See commit 16e4d93f6de7
("NFSD: Ignore client's source port on RDMA transports").
The Linux NFS server's DRC resolves XID collisions from the same
source IP address by using the checksum of the first 200 bytes of
the RPC call header.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Cc: stable@vger.kernel.org # v4.14+
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd')
0 files changed, 0 insertions, 0 deletions