diff options
| author | 2018-08-15 21:35:45 -0400 | |
|---|---|---|
| committer | 2018-08-16 13:47:09 -0400 | |
| commit | ea51f94b45a0fd657c61206c1b648cc72f95befa (patch) | |
| tree | 53dc98c4c920a71505c21750cd1537487daa9c91 /kernel/sysctl.c | |
| parent | pNFS: When updating the stateid in layoutreturn, also update the recall range (diff) | |
| download | wireguard-linux-ea51f94b45a0fd657c61206c1b648cc72f95befa.tar.xz wireguard-linux-ea51f94b45a0fd657c61206c1b648cc72f95befa.zip | |
pNFS: Treat RECALLCONFLICT like DELAY...
Yes, it is possible to get trapped in a loop, but the server should be
administratively revoking the recalled layout if it never gets returned.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'kernel/sysctl.c')
0 files changed, 0 insertions, 0 deletions
