From: Luis Henriques <luis.henriques@canonical.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Miller <davem@davemloft.net>,
stable <stable@vger.kernel.org>, netdev <netdev@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 3.2-3.12] skbuff: skb_segment: orphan frags before copying
Date: Mon, 9 Jun 2014 14:29:01 +0100 [thread overview]
Message-ID: <20140609132901.GD3591@hercules> (raw)
In-Reply-To: <1402070968.23860.9.camel@deadeye.wl.decadent.org.uk>
On Fri, Jun 06, 2014 at 05:09:28PM +0100, Ben Hutchings wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
>
> commit 1fd819ecb90cc9b822cd84d3056ddba315d3340f upstream.
>
> skb_segment copies frags around, so we need
> to copy them carefully to avoid accessing
> user memory after reporting completion to userspace
> through a callback.
>
> skb_segment doesn't normally happen on datapath:
> TSO needs to be disabled - so disabling zero copy
> in this case does not look like a big deal.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> [bwh: Backported to 3.2. As skb_segment() only supports page-frags *or* a
> frag list, there is no need for the additional frag_skb pointer or the
> preparatory renaming.]
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> This is what I used in Debian for 3.2, and I believe it applies to all
> stable branches up to 3.12 inclusive.
>
> For branches older than 3.6, this requires cherry-picking commit
> a353e0ce0fd4 ('skbuff: add an api to orphan frags'). To avoid breaking
> OOT builds of openvswitch, which will use skb_orphan_frags() if
> available, it is also necessary to cherry-pick commit dcc0fb782b3a
> ('skbuff: export skb_copy_ubufs').
>
> Ben.
>
Thanks Ben, I'll queue it for the 3.11 kernel.
Cheers,
--
Luís
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -2701,6 +2701,9 @@ struct sk_buff *skb_segment(struct sk_bu
> skb_put(nskb, hsize), hsize);
>
> while (pos < offset + len && i < nfrags) {
> + if (unlikely(skb_orphan_frags(skb, GFP_ATOMIC)))
> + goto err;
> +
> *frag = skb_shinfo(skb)->frags[i];
> __skb_frag_ref(frag);
> size = skb_frag_size(frag);
>
> --
> Ben Hutchings
> You can't have everything. Where would you put it?
next prev parent reply other threads:[~2014-06-09 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 16:09 [PATCH 3.2-3.12] skbuff: skb_segment: orphan frags before copying Ben Hutchings
2014-06-09 13:29 ` Luis Henriques [this message]
2014-06-28 0:57 ` Greg KH
[not found] <20140410.215420.576903689381200176.davem@davemloft.net>
[not found] ` <1397392513.10849.75.camel@deadeye.wl.decadent.org.uk>
2014-04-13 22:57 ` Ben Hutchings
2014-04-13 23:20 ` David Miller
2014-04-13 23:50 ` Ben Hutchings
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=20140609132901.GD3591@hercules \
--to=luis.henriques@canonical.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mst@redhat.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 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).