Skip to content

Commit e8d975e

Browse files
olgakorn1trondmypd
authored andcommitted
fixing infinite OPEN loop in 4.0 stateid recovery
Problem: When an operation like WRITE receives a BAD_STATEID, even though recovery code clears the RECLAIM_NOGRACE recovery flag before recovering the open state, because of clearing delegation state for the associated inode, nfs_inode_find_state_and_recover() gets called and it makes the same state with RECLAIM_NOGRACE flag again. As a results, when we restart looking over the open states, we end up in the infinite loop instead of breaking out in the next test of state flags. Solution: unset the RECLAIM_NOGRACE set because of calling of nfs_inode_find_state_and_recover() after returning from calling recover_open() function. Signed-off-by: Olga Kornievskaia <[email protected]> Cc: [email protected] Signed-off-by: Trond Myklebust <[email protected]>
1 parent c65b99f commit e8d975e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

fs/nfs/nfs4state.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1482,6 +1482,8 @@ static int nfs4_reclaim_open_state(struct nfs4_state_owner *sp, const struct nfs
14821482
spin_unlock(&state->state_lock);
14831483
}
14841484
nfs4_put_open_state(state);
1485+
clear_bit(NFS4CLNT_RECLAIM_NOGRACE,
1486+
&state->flags);
14851487
spin_lock(&sp->so_lock);
14861488
goto restart;
14871489
}

0 commit comments

Comments
 (0)