linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bug ?] Permanent FIN_WAIT_2 state on NFS client with bad NFS server
@ 2017-09-20 22:17 Manjunath Patil
  2017-09-21 17:05 ` David Wysochanski
  0 siblings, 1 reply; 8+ messages in thread
From: Manjunath Patil @ 2017-09-20 22:17 UTC (permalink / raw)
  To: linux-nfs

Hi,

With autoclose trying to close the connection, after the idle timeout
in NFSv3 mounts,
a bad NFS server may not send the final FIN, leading the client stay
in FIN_WAIT_2 state forever.
This is easily reproducible by simulating the bad server behavior. I
used 'netstat -an | grep 2049' to observer socket state.

This is will also stall the other RPC requests from connecting and
proceeding as XPRT_CLOSING flag is already set.

This can be observed in the 4.14-rc1 as well.
This behavior is introduced with the following commit -
caf4ccd SUNRPC: Make xs_tcp_close() do a socket shutdown rather than a
sock_release

Once we reverse this commit, the FIN_WAIT_2 state lasts only for 60 seconds.

Any thoughts correcting this behavior?
or is this behavior expected?

-Thanks,
Manjunath

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-10-08 17:58 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-20 22:17 [Bug ?] Permanent FIN_WAIT_2 state on NFS client with bad NFS server Manjunath Patil
2017-09-21 17:05 ` David Wysochanski
2017-09-22 19:21   ` Manjunath Patil
2017-10-06 19:13     ` Manjunath Patil
2017-10-06 20:51       ` Trond Myklebust
2017-10-06 22:12         ` Manjunath Patil
2017-10-06 22:38           ` Trond Myklebust
2017-10-08 17:58           ` Trond Myklebust

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).