diff options
author | Trond Myklebust <trond.myklebust@primarydata.com> | 2016-09-22 13:38:59 -0400 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2016-09-27 14:33:44 -0400 |
commit | 45870d6909d5a1f702d2a3781d8fc831301d13c8 (patch) | |
tree | 9343039cc514fcd1b462a0d633292ffb82256c06 /fs/dlm/dir.c | |
parent | 41020b671aa553f31e766fd1e9d38598eba72bd6 (diff) | |
download | linux-stable-45870d6909d5a1f702d2a3781d8fc831301d13c8.tar.gz linux-stable-45870d6909d5a1f702d2a3781d8fc831301d13c8.tar.bz2 linux-stable-45870d6909d5a1f702d2a3781d8fc831301d13c8.zip |
NFSv4.1: Test delegation stateids when server declares "some state revoked"
According to RFC5661, if any of the SEQUENCE status bits
SEQ4_STATUS_EXPIRED_ALL_STATE_REVOKED,
SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED, SEQ4_STATUS_ADMIN_STATE_REVOKED,
or SEQ4_STATUS_RECALLABLE_STATE_REVOKED are set, then we need to use
TEST_STATEID to figure out which stateids have been revoked, so we
can acknowledge the loss of state using FREE_STATEID.
While we already do this for open and lock state, we have not been doing
so for all the delegations.
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>
Diffstat (limited to 'fs/dlm/dir.c')
0 files changed, 0 insertions, 0 deletions