diff options
| author | Anna Schumaker <[email protected]> | 2024-04-25 16:24:29 -0400 |
|---|---|---|
| committer | Trond Myklebust <[email protected]> | 2024-05-20 11:37:15 -0400 |
| commit | f06d1b10cb016d5aaecdb1804fefca025387bd10 (patch) | |
| tree | c419fa88261324df9acd7b7ceccbdbc2371912b2 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 0dc9f430027b8bd9073fdafdfcdeb1a073ab5594 (diff) | |
NFS: Fix READ_PLUS when server doesn't support OP_READ_PLUS
Olga showed me a case where the client was sending multiple READ_PLUS
calls to the server in parallel, and the server replied
NFS4ERR_OPNOTSUPP to each. The client would fall back to READ for the
first reply, but fail to retry the other calls.
I fix this by removing the test for NFS_CAP_READ_PLUS in
nfs4_read_plus_not_supported(). This allows us to reschedule any
READ_PLUS call that has a NFS4ERR_OPNOTSUPP return value, even after the
capability has been cleared.
Reported-by: Olga Kornievskaia <[email protected]>
Fixes: c567552612ec ("NFS: Add READ_PLUS data segment support")
Cc: [email protected] # v5.10+
Signed-off-by: Anna Schumaker <[email protected]>
Reviewed-by: Benjamin Coddington <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions