From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [REVERT] blktap2: Use RING_COPY_REQUEST
Date: Wed, 11 May 2016 14:44:19 +0100 [thread overview]
Message-ID: <20160511134419.GA8063@citrix.com> (raw)
In-Reply-To: <57331EE702000078000EA822@prv-mh.provo.novell.com>
On Wed, May 11, 2016 at 04:00:39AM -0600, Jan Beulich wrote:
> >>> On 02.05.16 at 12:16, <wei.liu2@citrix.com> wrote:
> > On Fri, Apr 22, 2016 at 02:44:25AM -0600, Jan Beulich wrote:
> >> Short of getting any feedback on the previous discussion item
> >> http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg00571.html
> >> here's a formal revert request: Please revert commit 19f6c522a6
> >> from the staging tree (afaict it didn't get mirrored to any of the
> >> stable trees yet), as the changes it does are not necessary and
> >> possibly misleading.
> >
> > FWIW your analysis in the other thread makes sense to me. There doesn't
> > seem to be interaction between untrusted frontend and backend.
>
> Since there was no further follow-up: Can the above be taken as
> an ack (and a release ack for one)?
>
Doesn't this need an ack from member(s) of the security team before it
can be committed? It is related to an XSA after all.
I don't have clear idea how to proceed in this case TBH. In any case:
Acked-by: Wei Liu <wei.liu2@citrix.com>
And subject to an ack from security team member:
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
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-11 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 8:44 [REVERT] blktap2: Use RING_COPY_REQUEST Jan Beulich
2016-05-02 8:37 ` Ping: " Jan Beulich
2016-05-02 10:16 ` Wei Liu
2016-05-11 10:00 ` Jan Beulich
2016-05-11 13:44 ` Wei Liu [this message]
2016-05-11 14:00 ` Konrad Rzeszutek Wilk
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=20160511134419.GA8063@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--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 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).