From: Martin Pool <mbp@samba.org>
To: "David S. Miller" <davem@redhat.com>
Cc: kuznet@ms2.inr.ac.ru, ak@muc.de, netdev@oss.sgi.com, Alan.Cox@linux.org
Subject: Re: FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case
Date: Mon, 30 Sep 2002 19:59:10 +1000 [thread overview]
Message-ID: <20020930095909.GA8063@toey.sourcefrog.net> (raw)
In-Reply-To: <20020926.134608.31605412.davem@redhat.com>
On 26 Sep 2002, "David S. Miller" <davem@redhat.com> wrote:
> From: kuznet@ms2.inr.ac.ru
> Date: Thu, 26 Sep 2002 17:09:11 +0400 (MSD)
>
> I do not understand why tcp_push_pending_frames() was not used
> there... maybe, there was some reason not to use it.
>
> Dave, do you not remember this?
So where does this leave us?
Was the patch we came up with correct? It looks reasonable to me, but
I don't know the stack well enough to be sure. I think it would be
nice if it could be fixed in 2.2.
Let me know if there's anything I can do by way of testing, etc.
--
Martin
next prev parent reply other threads:[~2002-09-30 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 2:03 FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case Martin Pool
2002-09-18 1:58 ` David S. Miller
2002-09-18 2:09 ` Martin Pool
2002-09-18 23:38 ` Alexey Kuznetsov
2002-09-26 5:47 ` Martin Pool
2002-09-26 13:09 ` kuznet
2002-09-26 20:46 ` David S. Miller
2002-09-30 9:59 ` Martin Pool [this message]
2002-09-30 10:32 ` David S. Miller
2002-09-30 12:23 ` Alan Cox
2002-10-03 3:30 ` James Morris
2002-10-03 3:54 ` Andi Kleen
2002-10-03 7:59 ` David S. Miller
2002-10-03 7:56 ` David S. Miller
2002-09-18 2:30 ` Martin Pool
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 15:06 James Morris
2002-10-04 23:27 ` Martin Pool
2002-10-05 7:51 ` Martin Pool
2002-10-05 11:53 ` James Morris
2002-10-08 10:21 ` Martin Pool
2002-10-08 10:28 ` James Morris
2002-10-10 16:36 ` James Morris
2002-10-10 16:43 ` James Morris
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=20020930095909.GA8063@toey.sourcefrog.net \
--to=mbp@samba.org \
--cc=Alan.Cox@linux.org \
--cc=ak@muc.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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).