From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chuck Lever Subject: Re: nfs client hang Date: Wed, 28 Jul 2010 13:37:20 -0400 Message-ID: <4C506AD0.4070608@oracle.com> References: <99613C19B13C5D40914FB8930657FA9303365708DE@uk-ex-mbx1.terastack.bluearc.com> <4C4E89D4.8040607@bluearc.com> <1280233276.2827.175.camel@edumazet-laptop> <4C4F174C.2000308@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , "Linux Kernel Mailing List (linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)" , Trond Myklebust , netdev , Linux NFS Mailing List To: Andy Chittenden Return-path: In-Reply-To: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On 07/28/10 03:24 AM, Andy Chittenden wrote: > resending as it seems to have been corrupted on LKML! > >> The RPC client marks the socket closed. and the linger timeout is >> cancelled. At this point, sk_shutdown should be set to zero, correct? >> I don't see an xs_error_report() call here, which would confirm that the >> socket took a trip through tcp_disconnect(). > > From my reading of tcp_disconnect(), it calls sk->sk_error_report(sk) > unconditionally so as there's no xs_error_report(), that surely means > the exact opposite: tcp_disconnect() wasn't called. If it's not > called, sk_shutdown is not cleared. And my revised tracing confirmed > that it was set to SEND_SHUTDOWN. Sorry, that's what I meant above. An xs_error_report() debugging message at that point in the log would confirm that the socket took a trip through tcp_disconnect(). But I don't see such a message. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html