All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
To: "Stephen Hemminger" <shemminger@osdl.org>,
	"Herbert Xu" <herbert@gondor.apana.org.au>
Cc: <netdev@vger.kernel.org>
Subject: RE: [IPV6] Q: corrupt checksums when transferring data
Date: Fri, 25 Aug 2006 13:25:25 -0700	[thread overview]
Message-ID: <36D9DB17C6DE9E40B059440DB8D95F5281CD11@orsmsx418.amr.corp.intel.com> (raw)

Stephen Hemminger wrote:
> On Fri, 25 Aug 2006 11:13:48 -0700
> "Brandeburg, Jesse" <jesse.brandeburg@intel.com> wrote:
> 
>> I'm enabling e1000 to offload IPv6 since the 2.6.18+ kernels support
>> it. The kernel I'm testing is 2.6.18-rc4.
> 
> Yes, something is wrong with the GSO code. I am bisecting this bug
> 	http://bugzilla.kernel.org/show_bug.cgi?id=7050
> 
> 
> It looks like GSO is handing an IPV6 segment down to the sky2 driver
> even though it asks for only NETIF_F_TSO.

Ah ha, I was wondering if that bug report on sky2 might be related to
this issue.  E1000 actually sends the data I think (it just has a bad
checksum) when handed a too long frame.  Seems like the stack should
never give us something longer than the MTU + enet header, esp with all
hardware offloads disabled.

So I have a very easy repro with netperf
on remote: netserver -4 -6
netperf -H lh2-6,6 -t TCP_MAERTS -- -m4K -S128K -s128K

The remote will generate the bad frames.

Jesse

             reply	other threads:[~2006-08-25 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 20:25 Brandeburg, Jesse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-25 23:23 [IPV6] Q: corrupt checksums when transferring data Brandeburg, Jesse
2006-08-25 18:13 Brandeburg, Jesse
2006-08-25 18:50 ` Stephen Hemminger

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=36D9DB17C6DE9E40B059440DB8D95F5281CD11@orsmsx418.amr.corp.intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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.