From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: [PATCH 0/4] XSA-52..54 follow-up
Date: Tue, 04 Jun 2013 11:00:04 +0100 [thread overview]
Message-ID: <CDD37934.28A25%keir.xen@gmail.com> (raw)
In-Reply-To: <51ADBA6102000078000DAEAA@nat28.tlf.novell.com>
On 04/06/2013 08:58, "Jan Beulich" <JBeulich@suse.com> wrote:
> The first patch really isn't as much of a follow-up than what triggered
> the security issues to be noticed in the first place.
>
> 1: x86: preserve FPU selectors for 32-bit guest code
> 2: x86: fix XCR0 handling
> 3: x86/xsave: adjust state management
> 4: x86/fxsave: bring in line with recent xsave adjustments
>
> The first two I would see as candidates for 4.3 (as well as
> subsequent backporting, albeit I realize that especially the first
> one is non-trivial), while the third is code improvement only,
> and the fourth is really just cleanup, and hence I'd be fine with
> deferring them until after 4.3.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
I like the patches, 1 & 2 are good bug fixes.
Acked-by: Keir Fraser <keir@xen.org>
Patch #1 is quite scary though! I wonder really whether these long-lived
issues must be fixed right now, let alone backported?
-- Keir
next prev parent reply other threads:[~2013-06-04 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 7:58 [PATCH 0/4] XSA-52..54 follow-up Jan Beulich
2013-06-04 8:05 ` [PATCH 1/4] x86: preserve FPU selectors for 32-bit guest code Jan Beulich
2013-06-04 8:07 ` [PATCH 2/4] x86: fix XCR0 handling Jan Beulich
2013-06-04 8:09 ` [PATCH 3/4] x86/xsave: adjust state management Jan Beulich
2013-06-04 8:10 ` [PATCH 4/4] x86/fxsave: bring in line with recent xsave adjustments Jan Beulich
2013-06-04 10:00 ` Keir Fraser [this message]
2013-06-04 10:09 ` [PATCH 0/4] XSA-52..54 follow-up George Dunlap
2013-06-04 10:45 ` Jan Beulich
2013-06-04 10:47 ` George Dunlap
2013-06-04 13:58 ` Jan Beulich
2013-06-04 14:55 ` George Dunlap
2013-06-04 10:32 ` Jan Beulich
2013-06-04 12:43 ` Ben Guthro
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=CDD37934.28A25%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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).