From: NeilBrown <neilb@suse.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Richard Laager <rlaager@wiktel.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: PROBLEM: NFS Client Ignores TCP Resets
Date: Tue, 03 Oct 2017 09:13:48 +1100 [thread overview]
Message-ID: <878tgt42qr.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAN-5tyG7BeAoy_tqap23CM8rCHcyOcy2Jee3us+xU4kxVV54gA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Mon, Oct 02 2017, Olga Kornievskaia wrote:
> Hi Neil,
>
> Was your patch 3ffbc1d6558 (net/sunrpc/xprt_sock: fix regression in
> connection error reporting) is an attempt to fix this problem or was
> it something else (latter is what I think but would like to verify)?
That patch fixed a bit that was introduced in 4.12. As you reported a
problem with 4.5, it must be a different problem.
>
> I was wondering if there was anything done upstream that fixed this issue.
>
Not that I know of. I don't think it can be reproduced upstream, which
make it difficult.
The last think I said was:
>>
>> It might help to see a tcpdump trace of the case where the "ssh"
>> connection was broken successfully for comparison with the case where
>> the nfs connection wasn't broken. Or it might not.
Seeing the trace might not help, but not seeing (which is the current
situation) definitely won't help.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-02 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 2:24 PROBLEM: NFS Client Ignores TCP Resets Richard Laager
2016-03-08 17:06 ` Richard Laager
2016-03-09 21:16 ` Anna Schumaker
2016-03-09 21:42 ` Richard Laager
2016-03-11 9:44 ` Richard Laager
2016-04-02 1:43 ` Richard Laager
2016-04-03 3:58 ` NeilBrown
2016-04-07 9:45 ` Richard Laager
2016-04-08 0:47 ` NeilBrown
2017-10-02 19:29 ` Olga Kornievskaia
2017-10-02 22:13 ` NeilBrown [this message]
[not found] ` <CAN-5tyHuuBJxwqFLkiZa5ktBk7ypCJxmZ9creeD_RGWbK4Xn3A@mail.gmail.com>
2017-10-02 19:48 ` Richard Laager
2017-10-02 22:03 ` Olga Kornievskaia
2017-10-03 0:09 ` Richard Laager
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=878tgt42qr.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=aglo@umich.edu \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rlaager@wiktel.com \
--cc=trond.myklebust@primarydata.com \
/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).