From: Mark Salter <msalter@redhat.com>
To: grante@visi.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot sends continuous ACKS in TIME_WAIT state.
Date: Mon, 26 Mar 2001 18:56:00 -0000 [thread overview]
Message-ID: <200103270257.f2R2vFV16444@deneb.localdomain> (raw)
In-Reply-To: <20010326194931.A7833@visi.com>
>>>>> Grant Edwards writes:
> Following __tcp_close() on a socket, the RedBoot TCP stack
> exchanges a continuous stream of ACKs with my Linux box. The
> RedBoot socket is in the TIME_WAIT state. Do we really want to
> send out ACKs in TIME_WAIT state?
For some reason, RedBoot is performing and active close. When I wrote
the tcp stack, it was for a gdb stub which was always going to keep
the connection open for as long as the other end wanted, so I don't
think active closes have ever been tested. There is probably a bug in
that part of the tcp stack. On the other hand, RedBoot should not be
doing an active close in the first place.
--Mark
next prev parent reply other threads:[~2001-03-26 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 17:49 Grant Edwards
2001-03-26 18:56 ` Mark Salter [this message]
2001-03-26 20:00 ` Grant Edwards
2001-03-27 6:03 ` Grant Edwards
2001-03-27 9:59 ` Grant Edwards
2001-03-27 10:31 ` Hugo Tyson
2001-03-27 11:29 ` Mark Salter
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=200103270257.f2R2vFV16444@deneb.localdomain \
--to=msalter@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.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 read-only IMAP folder(s) and NNTP newsgroup(s).