NFSv4.1: Handle SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED status bit correctly.
authorTrond Myklebust <trond.myklebust@primarydata.com>
Sun, 5 Jul 2015 19:12:06 +0000 (15:12 -0400)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Sun, 5 Jul 2015 19:46:38 +0000 (15:46 -0400)
commit8b895ce652dc73bcf42a0c24acfc0708a06ea7c3
treefa3d7e1ff7cde226cb3d67e6f579e086cc217e5e
parentb5872f0c67edf3714dd46f04d73c3644f3addaf9
NFSv4.1: Handle SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED status bit correctly.

If the server tells us that only some state has been revoked, then we
need to run the full TEST_STATEID dog and pony show in order to discover
which locks and delegations are still OK. Currently we blow away all
state, which means that we lose all locks!

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4state.c