From: Luis Henriques <luis.henriques@canonical.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, stable <stable@vger.kernel.org>,
Florian Westphal <fw@strlen.de>,
Brad Spengler <spender@grsecurity.net>
Subject: Re: net: make skb_gso_segment error handling more robust
Date: Tue, 19 May 2015 09:27:02 +0100 [thread overview]
Message-ID: <20150519082702.GA1899@ares> (raw)
In-Reply-To: <1430779135.4113.202.camel@decadent.org.uk>
On Mon, May 04, 2015 at 11:38:55PM +0100, Ben Hutchings wrote:
> Brad Spengler pointed out this commit as a candidate for stable:
>
> commit 330966e501ffe282d7184fde4518d5e0c24bc7f8
> Author: Florian Westphal <fw@strlen.de>
> Date: Mon Oct 20 13:49:17 2014 +0200
>
> net: make skb_gso_segment error handling more robust
>
> Some hunks need to be dropped for older branches as skb_gso_segment()
> has gained more users over the last few years.
>
Thanks Ben, I'll queue this for the 3.16 kernel.
Cheers,
--
Luís
next prev parent reply other threads:[~2015-05-19 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 22:38 net: make skb_gso_segment error handling more robust Ben Hutchings
2015-05-19 8:27 ` Luis Henriques [this message]
2015-06-15 3:39 ` Zefan Li
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=20150519082702.GA1899@ares \
--to=luis.henriques@canonical.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=spender@grsecurity.net \
--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 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).