From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] XSA-77: widen scope again
Date: Mon, 9 May 2016 12:20:19 +0100 [thread overview]
Message-ID: <20160509112019.GC12241@citrix.com> (raw)
In-Reply-To: <57308E2902000078000E974A@prv-mh.provo.novell.com>
On Mon, May 09, 2016 at 05:18:33AM -0600, Jan Beulich wrote:
> >>> On 09.05.16 at 12:56, <wei.liu2@citrix.com> wrote:
> > On Mon, May 09, 2016 at 03:31:52AM -0600, Jan Beulich wrote:
> >> But note that by not having it on the list for now, things don't
> >> change: As per the original XSA-77, the operation was deemed
> >> disaggregation unsafe (and hence by implication its use in stub
> >> domains made stub domains an unsafe / unsupported environment)
> >> anyway. IOW this consideration is orthogonal to the purpose of
> >> the patch we're discussing.
> >
> > Makes sense.
>
> May I translate this into an ack? Or would you prefer for it to be
> acked a security team member?
>
The latter. I think it is more appropriate for a security team member to
ack this patch.
Wei.
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-09 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 9:35 [PATCH] XSA-77: widen scope again Jan Beulich
2016-05-06 8:12 ` Ping: " Jan Beulich
2016-05-09 16:19 ` George Dunlap
2016-05-10 6:41 ` Jan Beulich
2016-05-06 14:26 ` Wei Liu
2016-05-09 9:31 ` Jan Beulich
2016-05-09 10:56 ` Wei Liu
2016-05-09 11:18 ` Jan Beulich
2016-05-09 11:20 ` Wei Liu [this message]
2016-05-09 14:16 ` Andrew Cooper
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=20160509112019.GC12241@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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.