| commit | 0a014a44a50839a8064618e959fae5bbc44c2fd5 | |
| author | Trond Myklebust <trond.myklebust@primarydata.com> | |
| Thu, 22 Sep 2016 17:38:51 +0000 (22 13:38 -0400) | ||
| committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | |
| Tue, 27 Sep 2016 18:31:27 +0000 (27 14:31 -0400) | ||
| tree | d5817c8c204ed6f710f87a1fc1019283a6372351 | treesnapshot (tar.gz zip) |
| parent | 5690a22d8612e1788b48b4ea53c59868589cd2db | commitdiff |
NFSv4.1: Don't deadlock the state manager on the SEQUENCE status flags
As described in RFC5661, section 18.46, some of the status flags exist
in order to tell the client when it needs to acknowledge the existence of
revoked state on the server and/or to recover state.
Those flags will then remain set until the recovery procedure is done.
In order to avoid looping, the client therefore needs to ignore
those particular flags while recovering.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Tested-by: Oleg Drokin <green@linuxhacker.ru>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
As described in RFC5661, section 18.46, some of the status flags exist
in order to tell the client when it needs to acknowledge the existence of
revoked state on the server and/or to recover state.
Those flags will then remain set until the recovery procedure is done.
In order to avoid looping, the client therefore needs to ignore
those particular flags while recovering.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Tested-by: Oleg Drokin <green@linuxhacker.ru>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
| fs/nfs/nfs4_fs.h | diffblobblamehistory | |
| fs/nfs/nfs4proc.c | diffblobblamehistory | |
| fs/nfs/nfs4session.h | diffblobblamehistory | |
| fs/nfs/nfs4state.c | diffblobblamehistory |