From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: kaber@trash.net, maccetta@laurelnetworks.com, netdev@vger.kernel.org
Subject: Re: 2.6.20 crash in tcp_tso_segment()
Date: Tue, 13 Feb 2007 12:34:13 -0800 (PST) [thread overview]
Message-ID: <20070213.123413.35665346.davem@davemloft.net> (raw)
In-Reply-To: <20070213175121.GA27281@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 14 Feb 2007 04:51:21 +1100
> On Tue, Feb 13, 2007 at 03:34:43PM +0100, Patrick McHardy wrote:
> >
> > The callpath shows the REJECT target sending a TCP reset.
> > I'm guessing it has something to do with skb_copy_expand
> > copying the gso fields.
>
> Indeed. We need to reset the GSO bits there since the new
> packet is nothing like the one it's copied from.
>
> [NETFILTER]: Clear GSO bits for TCP reset packet
>
> The TCP reset packet is copied from the original. This
> includes all the GSO bits which do not apply to the new
> packet. So we should clear those bits.
>
> Spotted by Patrick McHardy.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> Something like this is needed for all trees with GSO.
> Actually it applies to TSO too although the effect there
> is a bit harder to notice.
Applied, thanks Herbert.
I'll push this to -stable.
I'm kind of challenged for time as I'll be out of town from
Wednesday until Sunday, so if someone could cook up the TSO
variable of the patch for pre-GSO kernels I'd appreciate it.
next prev parent reply other threads:[~2007-02-13 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:57 2.6.20 crash in tcp_tso_segment() Mike Accetta
2007-02-09 20:12 ` Herbert Xu
2007-02-13 14:34 ` Patrick McHardy
2007-02-13 16:18 ` Mike Accetta
2007-02-13 17:51 ` Herbert Xu
2007-02-13 20:34 ` David Miller [this message]
2007-02-13 21:51 ` Herbert Xu
2007-02-13 21:53 ` David Miller
2007-02-14 16:27 ` Mike Accetta
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=20070213.123413.35665346.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=maccetta@laurelnetworks.com \
--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;
as well as URLs for NNTP newsgroup(s).