From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: andyc.bluearc@gmail.com, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
eric.dumazet@gmail.com, William.Allen.Simpson@gmail.com,
gilad@codefidence.com, ilpo.jarvinen@helsinki.fi,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] [Bug 16494] NFS client over TCP hangs due to packet loss
Date: Tue, 3 Aug 2010 02:11:10 -0700 [thread overview]
Message-ID: <20100803021110.f0b3877b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100803.012144.267950450.davem@davemloft.net>
(cc linux-nfs)
On Tue, 03 Aug 2010 01:21:44 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: "Andy Chittenden" <andyc.bluearc@gmail.com>
> Date: Tue, 3 Aug 2010 09:14:31 +0100
>
> > I don't know whether this patch is the correct fix or not but it enables the
> > NFS client to recover.
> >
> > Kernel version: 2.6.34.1 and 2.6.32.
> >
> > Fixes <https://bugzilla.kernel.org/show_bug.cgi?id=16494>. It clears down
> > any previous shutdown attempts so that reconnects on a socket that's been
> > shutdown leave the socket in a usable state (otherwise tcp_sendmsg() returns
> > -EPIPE).
>
> If the SunRPC code wants to close a TCP socket then use it again,
> it should disconnect by doing a connect() with sa_family == AF_UNSPEC
next parent reply other threads:[~2010-08-03 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4c57cfe8.887b0e0a.2f79.4772@mx.google.com>
[not found] ` <20100803.012144.267950450.davem@davemloft.net>
2010-08-03 9:11 ` Andrew Morton [this message]
2010-08-03 10:25 ` [PATCH] [Bug 16494] NFS client over TCP hangs due to packet loss Andy Chittenden
2010-08-05 14:55 ` Andy Chittenden
2010-08-05 19:50 ` Trond Myklebust
2010-08-06 9:30 ` Andy Chittenden
2010-08-09 9:27 ` Andy Chittenden
2010-08-09 16:55 ` Trond Myklebust
2010-08-10 8:40 ` Andy Chittenden
2018-06-19 21:56 ` Joe Perches
2018-06-20 16:40 ` Andy C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100803021110.f0b3877b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=William.Allen.Simpson@gmail.com \
--cc=andyc.bluearc@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=gilad@codefidence.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).