From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 89831] New: timeout of TCP-sockets is *infinite* by default .. even if TCP-connection is already *broken*
Date: Sat, 3 Jan 2015 17:33:30 -0800 [thread overview]
Message-ID: <20150103173330.0f9b209b@urahara> (raw)
Begin forwarded message:
Date: Tue, 16 Dec 2014 22:33:50 -0800
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 89831] New: timeout of TCP-sockets is *infinite* by default .. even if TCP-connection is already *broken*
https://bugzilla.kernel.org/show_bug.cgi?id=89831
Bug ID: 89831
Summary: timeout of TCP-sockets is *infinite* by default ..
even if TCP-connection is already *broken*
Product: Networking
Version: 2.5
Kernel Version: all
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: polymorphm@gmail.com
Regression: No
Created attachment 160881
--> https://bugzilla.kernel.org/attachment.cgi?id=160881&action=edit
test for catch infinite freezing (on TCP-sockets by default) on GNU/Linux
good day!
please, very sorry me for your time. :-) [and sorry for my bad english].
big problem in that fact: *most* application-programmers think that if
TCP-connection is already *broken* -- that timeout of TCP-socket will *NOT* be
*infinite*. (default system timeout).
I prepared example code:
https://gist.github.com/polymorphm/0e057402c9fa82547d72 (and this file
"to-test.c" -- in attachment).
this example code ("to-test.c") -- shows that if TCP-connection *broken* --
that timeout will *never* be reached (for broken TCP-connection. EVEN AFTER
SOME DAYS).
program "to-test.c" -- becomes to infinite freezing -- after "[step 8]":
$ gcc -Wall -Werror -o to-test to-test.c && sudo ./to-test
***** begin of test *****
[step 1] creating socket...
***** INFO: is used SO_KEEPALIVE by default for TCP-sockets? answer: 0
*****
[step 2] connecting socket...
[step 3] time waiting (1s)...
[step 4] breaking down network... [wlp1s0]
# ip link set down dev wlp1s0
[step 5] time waiting (15s)...
[step 6] reestablishing up network... [wlp1s0]
# ip link set up dev wlp1s0
[step 7] time waiting (1s)...
[step 8] waiting of socket timeout (or we are freezed *infinity*?)...
(infinite freeze -- at this point)
probably, this issue-ticket will be marked as WONTFIX (and again: very sorry me
for your time!). but this issue-ticket -- need at least for official canonical
URL-link for answer to problem of default timeout of *broken* TCP-connection on
GNU/Linux.
when I speek with some application-programmers -- they say me: if GNU/Linux
freeze at broken-TCP-connections (with default settings of socket) than is
*bug* of GNU/Linux. and I maked this issue-ticket. sorry.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-01-04 1:33 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=20150103173330.0f9b209b@urahara \
--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