NFSv4.1: Handle SEQ4_STATUS_RECALLABLE_STATE_REVOKED status bit correctly
authorTrond Myklebust <trond.myklebust@primarydata.com>
Sun, 5 Jul 2015 19:20:53 +0000 (15:20 -0400)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Sun, 5 Jul 2015 19:50:18 +0000 (15:50 -0400)
commit4099287feb5833c24b5a91e1fe55207cf7559350
tree86a9a28a10fdf16beaf8ae861f69f47e8d63c724
parent8b895ce652dc73bcf42a0c24acfc0708a06ea7c3
NFSv4.1: Handle SEQ4_STATUS_RECALLABLE_STATE_REVOKED status bit correctly

Try to handle this for now by invalidating all outstanding layouts for this
server and then testing all the open+lock+delegation stateids.
At some later stage, we may want to optimise by separating out the testing of
delegation stateids only, and adding testing of layout stateids.

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