netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, aabdulla@nvidia.com, jgarzik@pobox.com,
	manfred@colorfullife.com, stable@kernel.org
Subject: Re: [patch for 2.6.27? 4/5] forcedeth: fix checksum flag
Date: Wed, 27 Aug 2008 05:57:23 -0400	[thread overview]
Message-ID: <48B52503.8070309@garzik.org> (raw)
In-Reply-To: <200808202334.m7KNYbpF005035@imap1.linux-foundation.org>

akpm@linux-foundation.org wrote:
> From: Ayaz Abdulla <aabdulla@nvidia.com>
> 
> Fix the checksum feature advertised in device flags.  The hardware support
> TCP/UDP over IPv4 and TCP/UDP over IPv6 (without IPv6 extension headers). 
> However, the kernel feature flags do not distinguish IPv6 with/without
> extension headers.
> 
> Therefore, the driver needs to use NETIF_F_IP_CSUM instead of
> NETIF_F_HW_CSUM since the latter includes all IPv6 packets.
> 
> A future patch can be created to check for extension headers and perform
> software checksum calculation.
> 
> Signed-off-by: Ayaz Abdulla <aabdulla@nvidia.com>
> Cc: Jeff Garzik <jgarzik@pobox.com>
> Cc: Manfred Spraul <manfred@colorfullife.com
> Cc: <stable@kernel.org>		[2.6.25.x, 2.6.26.x]
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

applied, although for future reference, read the top of 
include/linux/skbuff.h, most notably:

  *          NOTE: Even if device supports only some protocols, but
  *          is able to produce some skb->csum, it MUST use COMPLETE,
  *          not UNNECESSARY.


      reply	other threads:[~2008-08-27  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 23:34 [patch for 2.6.27? 4/5] forcedeth: fix checksum flag akpm
2008-08-27  9:57 ` Jeff Garzik [this message]

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=48B52503.8070309@garzik.org \
    --to=jeff@garzik.org \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=jgarzik@pobox.com \
    --cc=manfred@colorfullife.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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).