From: Ben Hutchings <ben@decadent.org.uk>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, sri@us.ibm.com,
David Miller <davem@davemloft.net>
Subject: Re: [net-next-2.6 PATCH] Fix IPv6 GSO type checks in Intel ethernet drivers
Date: Sat, 23 Jan 2010 14:52:55 +0000 [thread overview]
Message-ID: <1264258375.373.53.camel@localhost> (raw)
In-Reply-To: <20100123.012723.129767377.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Sat, 2010-01-23 at 01:27 -0800, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Sat, 23 Jan 2010 01:24:45 -0800
>
> > From: Sridhar Samudrala <sri@us.ibm.com>
> >
> > Found this problem when testing IPv6 from a KVM guest to a remote
> > host via e1000e device on the host.
> > The following patch fixes the check for IPv6 GSO packet in Intel
> > ethernet drivers to use skb_is_gso_v6(). SKB_GSO_DODGY is also set
> > when packets are forwarded from a guest.
> >
> > Signed-off-by: Sridhar Samudrala <sri@us.ibm.com>
> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>
> This is definitely net-2.6 material, the bug definitely exists
> there and besides the ixgbevf bit, this patch applies cleanly
> to net-2.6 as well.
This is presumably suitable for stable as well; if so, please cc
stable@kernel.org.
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2010-01-23 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 9:24 [net-next-2.6 PATCH] Fix IPv6 GSO type checks in Intel ethernet drivers Jeff Kirsher
2010-01-23 9:27 ` David Miller
2010-01-23 9:31 ` Jeff Kirsher
2010-01-23 14:52 ` Ben Hutchings [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=1264258375.373.53.camel@localhost \
--to=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.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 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.