]> CyberLeo.Net >> Repos - FreeBSD/FreeBSD.git/commit
MFC: r316717
authorrmacklem <rmacklem@FreeBSD.org>
Wed, 26 Apr 2017 22:11:44 +0000 (22:11 +0000)
committerrmacklem <rmacklem@FreeBSD.org>
Wed, 26 Apr 2017 22:11:44 +0000 (22:11 +0000)
commitf3bdd48d1c3c2f2cda15fd4801f8f8c9dabdae26
tree6ccf8a378c5d1d8f66af1fb807ed5f2197680059
parent5240eda1f022379168b993714c314ab8fb78ea56
MFC: r316717
During a server crash recovery, fix the NFSv4.1 client for a NFSERR_BADSESSION
during recovery.

If the NFSv4.1 client gets a NFSv4.1 NFSERR_BADSESSION reply to an Open/Lock
operation while recovering from the server crash/reboot, allow the opens
to be retained for a subsequent recovery attempt. Since NFSv4.1 servers
should only reply NFSERR_BADSESSION after a crash/reboot that has lost
state, this case should almost never happen.
However, for the AmazonEFS file service, this has been observed when
the client does a fresh TCP connection for RPCs.
sys/fs/nfsclient/nfs_clstate.c