From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 73021] New: TCP_USER_TIMEOUT not working when interface is taken down, e.g. cable unplugged
Date: Thu, 27 Mar 2014 09:02:02 -0700 [thread overview]
Message-ID: <20140327090202.673380a1@samsung-9> (raw)
Begin forwarded message:
Date: Thu, 27 Mar 2014 05:49:28 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 73021] New: TCP_USER_TIMEOUT not working when interface is taken down, e.g. cable unplugged
https://bugzilla.kernel.org/show_bug.cgi?id=73021
Bug ID: 73021
Summary: TCP_USER_TIMEOUT not working when interface is taken
down, e.g. cable unplugged
Product: Networking
Version: 2.5
Kernel Version: 3.4.24 and 3.11.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: pelle.johnsen@gmail.com
Regression: No
When the network interface is taken down (in this case eth0 plugging out cable)
an established socket goes to zero window probing state (netstat -o shows
unkn-4). This state ignores TCP_USER_TIMEOUT (and any keep-alive timeouts) and
result is that socket takes ~12 min. to timeout instead of what is specified
with TCP_USER_TIMEOUT.
There seems to be 2 'issues':
1. Why does socket go to zero window probing in this case?
2. Why does zero window probing not respect TCP_USER_TIMEOUT?
Expected behavior:
TCP_USER_TIMEOUT can be used to limit how long it takes a socket to timeout.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-03-27 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140327090202.673380a1@samsung-9 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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