netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: david@davidcoulson.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: warning at net/core/dev.c:1171/skb_checksum_help() 2.6.18-rc3
Date: Mon, 31 Jul 2006 07:07:31 +0200	[thread overview]
Message-ID: <44CD9013.7020401@trash.net> (raw)
In-Reply-To: <20060730.215907.58439803.davem@davemloft.net>

David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Mon, 31 Jul 2006 06:24:31 +0200
> 
> 
>>This is a known problem with NAT and HW checksum and will probably get
>>fixed in 2.6.19.
> 
> 
> I would like to see this fixed for 2.6.18, no later.
> 
> Either that or disable the bug trap, but taking this route
> is severely discouraged. :)


I'm actually updateing my patch for this on top of Herbert's
CHECKSUM_PARTIAL patch right now. Unfortunately I targeted 2.6.19,
so the fixes are on top of a few cleanups (which unconvered a few
unrelated bugs as well). I'll post it when I'm done so we can
decide how to proceed.


  reply	other threads:[~2006-07-31  5:07 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  4:16 BUG: warning at net/core/dev.c:1171/skb_checksum_help() 2.6.18-rc3 David Coulson
2006-07-31  4:24 ` Patrick McHardy
2006-07-31  4:59   ` David Miller
2006-07-31  5:07     ` Patrick McHardy [this message]
2006-07-31 10:39       ` Patrick McHardy
2006-07-31 11:30         ` Herbert Xu
2006-07-31 18:36           ` Patrick McHardy
2006-07-31 21:15             ` David Miller
2006-07-31 21:36               ` Patrick McHardy
2006-07-31 21:54                 ` David Miller
2006-08-01  7:00             ` David Miller
2006-08-01  7:04               ` Herbert Xu
2006-08-01  7:22               ` Patrick McHardy
2006-08-01 15:34               ` Phil Oester
2006-08-01 22:04                 ` Herbert Xu
2006-08-01  7:19             ` Patrick McHardy
2006-08-01  7:23               ` Herbert Xu
2006-08-01  7:36                 ` David Miller
2006-08-01  7:45                   ` Herbert Xu
2006-08-01 12:00                     ` Jamal Hadi Salim
2006-08-01 12:34                       ` Herbert Xu
2006-08-01 12:55                         ` Jamal Hadi Salim
2006-08-01  7:38                 ` Patrick McHardy
2006-08-01 11:51               ` Herbert Xu
2006-08-03  9:21                 ` Patrick McHardy
2006-08-03  9:30                   ` Herbert Xu
2006-08-03  9:34                     ` Patrick McHardy
2006-08-01 12:29             ` Herbert Xu
2006-08-03  9:29               ` Patrick McHardy
2006-08-03  9:33                 ` Herbert Xu
2006-08-03  9:40                   ` Patrick McHardy
2006-08-03  9:57                     ` Herbert Xu
2006-08-05  7:13                       ` Patrick McHardy
2006-08-05  7:59                         ` Herbert Xu
2006-08-01 22:03             ` Herbert Xu
2006-08-03  9:30               ` Patrick McHardy
2006-08-02  0:49           ` Herbert Xu
2006-08-03  9:32             ` Patrick McHardy
2006-08-03  9:36               ` Herbert Xu
2006-08-03  9:43                 ` Patrick McHardy
2006-07-31  4:34 ` Andrew Morton
2006-07-31  4:42   ` David Coulson
2006-07-31  4:58   ` 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=44CD9013.7020401@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=david@davidcoulson.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).