netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Petersson, Mats" <Mats.Petersson@amd.com>,
	xen-devel@lists.xensource.com, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [Xen-devel] kernel BUG at net/core/dev.c:1133!
Date: Fri, 07 Jul 2006 22:06:08 +0200	[thread overview]
Message-ID: <44AEBEB0.8020704@trash.net> (raw)
In-Reply-To: <E1FyrUg-0003FA-00@gondolin.me.apana.org.au>

Herbert Xu wrote:
> Petersson, Mats <Mats.Petersson@amd.com> wrote:
> 
>>Looks like the GSO is involved?
> 
> 
> It's certainly what crashed your machine :) It's probably not the
> guilty party though.  Someone is passing through a TSO packet with
> checksum set to something other than CHECKSUM_HW.
> 
> I bet it's netfilter and we just never noticed before because real
> NICS would simply corrupt the checksum silently.
> 
> Could you confirm that you have netfilter rules (in particular NAT
> rules) and that this goes away if you flush all your netfilter tables?
> 
> Patrick, do we really have to zap the checksum on outbound NAT? Could
> we update it instead?

Are you refering to this code in ip_nat_fn()?

        /* If we had a hardware checksum before, it's now invalid */
        if ((*pskb)->ip_summed == CHECKSUM_HW)
                if (skb_checksum_help(*pskb, (out == NULL)))
                        return NF_DROP;

Doing incremental updates should work fine. This is something
I wanted to take care of at some point, but didn't get to it
yet.


  parent reply	other threads:[~2006-07-07 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <907625E08839C4409CE5768403633E0BA7FD76@sefsexmb1.amd.com>
2006-07-07 14:39 ` kernel BUG at net/core/dev.c:1133! Herbert Xu
2006-07-07 15:03   ` [Xen-devel] " Petersson, Mats
2006-07-08  2:03     ` Herbert Xu
2006-07-07 15:05   ` Tim Post
2006-07-07 16:48     ` Petersson, Mats
2006-07-07 20:06   ` Patrick McHardy [this message]
2006-07-08  2:04     ` [Xen-devel] " Herbert Xu

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=44AEBEB0.8020704@trash.net \
    --to=kaber@trash.net \
    --cc=Mats.Petersson@amd.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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).