From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Michael Tokarev <mjt@tls.msk.ru>, netdev@vger.kernel.org
Subject: Re: rare bad TCP checksum with 2.6.19?
Date: Tue, 16 Jan 2007 13:15:26 +0100 [thread overview]
Message-ID: <45ACC1DE.6090708@trash.net> (raw)
In-Reply-To: <20070116115053.GA16529@gondor.apana.org.au>
Herbert Xu wrote:
> On Tue, Jan 16, 2007 at 11:08:51AM +0300, Michael Tokarev wrote:
>
>>Ok. Here's another trace, from that remote network that triggers
>>this thing more-or-less reliable (every 2nd transfer at least) --
>>http://www.corpit.ru/mjt/bh-bad-cksum-dmp.bin . It's a full session
>>between 216.168.29.244 - the requesting/receiving side -- and
>>81.13.94.6 -- our sending side (the file being transferred is some
>>trojan horse I found on a friend's PC, so be careful ;)
>
>
> I'll have a look at this tomorrow.
>
> Since you're certain that this is being seen on the wire, one
> possibility is that we've got a bug somewhere that's zeroing
> skb->ip_summed on a packet with a partial checksum.
>
> One potential spot where this could happen is netfilter.
> Patrick, do you know of any recent changes (this is happening
> with 2.6.19) that might cause this?
The incremental HW checksum update stuff went in 2.6.19, so thats
a prime suspect. Can't see where this could be happening though.
Michael, how exactly is netfilter involved in your setup?
next prev parent reply other threads:[~2007-01-16 12:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 22:59 rare bad TCP checksum with 2.6.19? Michael Tokarev
2007-01-15 9:39 ` Herbert Xu
2007-01-15 13:34 ` Michael Tokarev
2007-01-15 14:25 ` Michael Tokarev
2007-01-15 18:13 ` Eric Dumazet
2007-01-15 19:33 ` Michael Tokarev
2007-01-15 23:36 ` Eric Dumazet
2007-01-15 20:10 ` Herbert Xu
2007-01-15 21:46 ` Michael Tokarev
2007-01-15 23:35 ` Herbert Xu
2007-01-16 3:27 ` Herbert Xu
2007-01-16 3:38 ` Herbert Xu
2007-01-16 8:08 ` Michael Tokarev
2007-01-16 11:50 ` Herbert Xu
2007-01-16 12:15 ` Patrick McHardy [this message]
2007-01-16 14:38 ` Michael Tokarev
2007-01-17 14:12 ` Michael Tokarev
2007-01-19 11:06 ` [PATCH] tcp_output: " Jarek Poplawski
2007-01-19 12:14 ` Patrick McHardy
2007-01-19 13:23 ` Michael Tokarev
2007-01-19 14:32 ` Jarek Poplawski
2007-01-19 13:20 ` Michael Tokarev
2007-01-19 14:08 ` Jarek Poplawski
2007-01-22 7:13 ` Jarek Poplawski
2007-01-22 7:19 ` Michael Tokarev
2007-01-22 8:03 ` Jarek Poplawski
2007-01-19 21:10 ` Herbert Xu
2007-01-22 6:52 ` Jarek Poplawski
2007-01-22 7:45 ` Herbert Xu
2007-01-22 8:48 ` Jarek Poplawski
2007-01-22 13:46 ` Patrick McHardy
2007-01-24 6:08 ` David Miller
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=45ACC1DE.6090708@trash.net \
--to=kaber@trash.net \
--cc=herbert@gondor.apana.org.au \
--cc=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.