From: Andre Tomt <andre@tomt.net>
To: netdev@oss.sgi.com
Cc: "David S. Miller" <davem@davemloft.net>, akpm@osdl.org
Subject: Re: Fw: 2.6.9 Oops in tcp_time_to_recover + 0x6d/0x1b0
Date: Thu, 28 Oct 2004 04:06:16 +0200 [thread overview]
Message-ID: <41805418.9030209@tomt.net> (raw)
In-Reply-To: <417F158E.4010109@tomt.net>
Andre Tomt wrote:
> David S. Miller wrote:
>
>> Current BK should have a fix for this from Herbert Xu.
>>
>
> is this what the
>
> [TCP]: Handle real partial-ACKs of TSO frames correctly.
> [TCP]: Only re-set TSO size for packet which was TSO to begin with.
> [TCP]: Fix tcp_trim_head() calculations.
>
> changesets fixed?
Sigh, I'm retarded. I was meaning to send this on-list, not off-list.
Silly fingers.
prev parent reply other threads:[~2004-10-28 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 23:38 Fw: 2.6.9 Oops in tcp_time_to_recover + 0x6d/0x1b0 Andrew Morton
2004-10-26 23:46 ` David S. Miller
[not found] ` <417F158E.4010109@tomt.net>
2004-10-28 2:06 ` Andre Tomt [this message]
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=41805418.9030209@tomt.net \
--to=andre@tomt.net \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--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).