diff options
| author |   Chuck Lever <chuck.lever@oracle.com> | 2019-01-09 10:04:57 -0500 |
|---|---|---|
| committer |   Anna Schumaker <Anna.Schumaker@Netapp.com> | 2019-01-15 15:36:41 -0500 |
| commit | deaa5c96c2f7e8b934088a1e70a0fe8797bd1149 (patch) | |
| tree | 8b78410665a7e6c1f52bbc3c9e7092953f5fc761 /fs | |
| parent | SUNRPC: Ensure we respect the RPCSEC_GSS sequence number limit (diff) | |
| download | linux-dev-deaa5c96c2f7e8b934088a1e70a0fe8797bd1149.tar.xz linux-dev-deaa5c96c2f7e8b934088a1e70a0fe8797bd1149.zip | |
SUNRPC: Address Kerberos performance/behavior regression
When using Kerberos with v4.20, I've observed frequent connection
loss on heavy workloads. I traced it down to the client underrunning
the GSS sequence number window -- NFS servers are required to drop
the RPC with the low sequence number, and also drop the connection
to signal that an RPC was dropped.
Bisected to commit 918f3c1fe83c ("SUNRPC: Improve latency for
interactive tasks").
I've got a one-line workaround for this issue, which is easy to
backport to v4.20 while a more permanent solution is being derived.
Essentially, tk_owner-based sorting is disabled for RPCs that carry
a GSS sequence number.
Fixes: 918f3c1fe83c ("SUNRPC: Improve latency for interactive ... ")
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions