public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug 1001523] New: RedBoot TCP socket stays in TIME_WAIT state forever
@ 2012-03-07 16:19 bugzilla-daemon
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2012-03-07 16:19 UTC (permalink / raw)
To: unassigned
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001523
Summary: RedBoot TCP socket stays in TIME_WAIT state forever
Product: eCos
Version: CVS
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: low
Component: RedBoot
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: stano@meduna.org
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=1623)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1623)
Move the do_close timer to wherever TIME_WAIT is entered
The bug reported in
http://sources.redhat.com/ml/ecos-discuss/2006-04/msg00034.html looks to be
still present in the current code.
To reproduce it is sufficient to change net_io_test so that it immediately does
__tcp_close(&tcp_sock) in the ESTABLISHED branch and add a diag_printf for the
socket state. The socket goes to _TIME_WAIT and never gets out of it.
The patch suggested by
http://sources.redhat.com/ml/ecos-discuss/2006-04/msg00035.html seems to fix
the problem. See attach for my patch.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug 1001523] New: RedBoot TCP socket stays in TIME_WAIT state forever
@ 2012-03-07 16:19 bugzilla-daemon
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2012-03-07 16:19 UTC (permalink / raw)
To: ecos-bugs
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001523
Summary: RedBoot TCP socket stays in TIME_WAIT state forever
Product: eCos
Version: CVS
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: low
Component: RedBoot
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: stano@meduna.org
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=1623)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1623)
Move the do_close timer to wherever TIME_WAIT is entered
The bug reported in
http://sources.redhat.com/ml/ecos-discuss/2006-04/msg00034.html looks to be
still present in the current code.
To reproduce it is sufficient to change net_io_test so that it immediately does
__tcp_close(&tcp_sock) in the ESTABLISHED branch and add a diag_printf for the
socket state. The socket goes to _TIME_WAIT and never gets out of it.
The patch suggested by
http://sources.redhat.com/ml/ecos-discuss/2006-04/msg00035.html seems to fix
the problem. See attach for my patch.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-03-07 16:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-03-07 16:19 [Bug 1001523] New: RedBoot TCP socket stays in TIME_WAIT state forever bugzilla-daemon
2012-03-07 16:19 bugzilla-daemon
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 read-only IMAP folder(s) and NNTP newsgroup(s).