From: Greg KH <greg@kroah.com>
To: Benjamin Poirier <bpoirier@suse.de>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, stable@vger.kernel.org,
Jesse Gross <jesse@nicira.com>
Subject: Re: [PATCH net/stable] gro: reset vlan_tci on reuse
Date: Sat, 26 Nov 2011 07:52:02 -0800 [thread overview]
Message-ID: <20111126155202.GA8467@kroah.com> (raw)
In-Reply-To: <1322320749-8055-1-git-send-email-bpoirier@suse.de>
On Sat, Nov 26, 2011 at 10:19:09AM -0500, Benjamin Poirier wrote:
> This one liner is part of upstream
> commit 3701e51382a026cba10c60b03efabe534fba4ca4
>
> and it is in the same vein as
> commit 66c46d741e2e60f0e8b625b80edb0ab820c46d7a
> commit 6d152e23ad1a7a5b40fef1f42e017d66e6115159
>
> which are already in -stable.
>
> For drivers using the vlan_gro_frags() interface, a packet with invalid tci
> leads to GRO_DROP and napi_reuse_skb(). The skb has to be sanitized before
> being reused or we'll send skb's with invalid vlan_tci up the stack where
> they're not expected.
>
> Signed-off-by: Benjamin Poirier <bpoirier@suse.de>
> Cc: Jesse Gross <jesse@nicira.com>
>
> ---
>
> Please note, reusing skb's with an invalid vlan_tci can cause panics on
> 2.6.32.y -stable kernels.
You forgot to mention what stable kernel tree(s) you want this patch
applied to. And why can't I just take all of
3701e51382a026cba10c60b03efabe534fba4ca4? (hint, when refering to git
commit ids, please put the description of what they are in () after them
so we have a hint and don't have to dig through a git tree to find
them.)
Also, I need David's ack before I can take this, or any other network
patch, for the stable tree.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-26 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 15:19 [PATCH net/stable] gro: reset vlan_tci on reuse Benjamin Poirier
2011-11-26 15:52 ` Greg KH [this message]
2011-11-27 1:01 ` Benjamin Poirier
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=20111126155202.GA8467@kroah.com \
--to=greg@kroah.com \
--cc=bpoirier@suse.de \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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 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.