diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-07-31 14:29:06 -0400 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-08-03 22:06:42 -0400 |
| commit | 14516c3a30e256e8d4e7a9af271c8df644ac3222 (patch) | |
| tree | ed8d43d6568fca893b7b1ebd7bc38244fc37a409 /fs/read_write.c | |
| parent | 0a8ebba943dd89bdd57c5dab5a66932f690847d9 (diff) | |
NFSv4.1: Handle NFS4ERR_DELAY on SEQUENCE correctly
In RFC5661, an NFS4ERR_DELAY error on a SEQUENCE operation has the special
meaning that the server is not finished processing the request. In this
case we want to just retry the request without touching the slot.
Also fix a bug whereby we would fail to update the sequence id if the
server returned any error other than NFS_OK/NFS4ERR_DELAY.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/read_write.c')
0 files changed, 0 insertions, 0 deletions