public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical•com>
To: Ian Campbell <Ian.Campbell@citrix•com>
Cc: <stable@vger•kernel.org>, "David S. Miller" <davem@davemloft•net>,
	xen-devel <xen-devel@lists•xen.org>, <netdev@vger•kernel.org>,
	Wei Liu <wei.liu2@citrix•com>
Subject: Re: xen-netback stable backports request (regression fixes)
Date: Tue, 28 May 2013 12:27:57 +0100	[thread overview]
Message-ID: <87wqqjpcn6.fsf@canonical.com> (raw)
In-Reply-To: <1369734465.3469.52.camel@zakaz.uk.xensource.com> (Ian Campbell's message of "Tue, 28 May 2013 10:47:45 +0100")

Ian Campbell <Ian.Campbell@citrix•com> writes:

> Hi Dave, stable folks,
>
> The following set of patches fix a xen netback regression caused by the
> fixes for CVE-2013-0216 / CVE-2013-0217 / XSA-39 (the original change
> was several patches starting at 48856286b64e), we'd like to see them
> backported to stable branches if possible. I think the fixups have now
> been in Linus tree since around the start of May.
>
> Wei and I are happy to help with backports if necessary. Some of the
> patches are cleanups which make backports easier but if you would prefer
> we could produce backports without them.
>
> 27f85228 xen-netback: remove skb in xen_netbk_alloc_page
> 2810e5b9 xen-netback: coalesce slots in TX path and fix regressions
> 03393fd5 xen-netback: don't disconnect frontend when seeing oversize packet
> ac69c26e xen-netback: remove redundent parameter in netbk_count_requests
> 59ccb4eb xen-netback: avoid allocating variable size array on stack
> 37641494 xen-netback: better names for thresholds
>
> In addition there are some useful related (but not security relevant)
> fixes to netfront:
>
> e2d617c0 xen-netfront: remove unused variable `extra'
> 7158ff6d xen-netfront: frags -> slots in xennet_get_responses
> 697089dc xen-netfront: frags -> slots in log message
> 9ecd1a75 xen-netfront: reduce gso_max_size to account for max TCP header

Thanks Ian.

For the 3.5 kernel, the only one that seems to cause problems is the
last one (9ecd1a75d977e2e8c48139c7d3efed183f898d94).  However, if I
also pick f36c374782e40a3812f729838b5b80d2ce601725 ("xen/netfront:
handle compound page fragments on transmit"), it applies cleanly.  Do
you see any problem picking this one as well?

Cheers,
-- 
Luis

  reply	other threads:[~2013-05-28 11:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  9:47 xen-netback stable backports request (regression fixes) Ian Campbell
2013-05-28 11:27 ` Luis Henriques [this message]
2013-05-31 13:20 ` [Xen-devel] " William Dauchy
2013-05-31 13:45   ` William Dauchy
2013-06-03 13:50     ` Ian Campbell
2013-06-05  4:55 ` Greg KH
2013-06-05  8:56   ` Ian Campbell
2013-06-05 20:25     ` Greg KH
2013-06-05 20:52       ` Ian Campbell
2013-06-05 21:08         ` Greg KH
2013-06-05 21:10           ` [Xen-devel] " Ian Campbell
2013-06-05 13:19   ` Wei Liu
2013-06-13  2:38 ` 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=87wqqjpcn6.fsf@canonical.com \
    --to=luis.henriques@canonical$(echo .)com \
    --cc=Ian.Campbell@citrix$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stable@vger$(echo .)kernel.org \
    --cc=wei.liu2@citrix$(echo .)com \
    --cc=xen-devel@lists$(echo .)xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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