xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	committers@xenproject.org,
	George Dunlap <george.dunlap@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: Impact of HW vulnerabilities & Implications on Security Vulnerability Process
Date: Thu, 8 Sep 2016 12:19:37 +0100	[thread overview]
Message-ID: <20160908111937.GD12697@citrix.com> (raw)
In-Reply-To: <22481.18326.348315.695336@mariner.uk.xensource.com>

On Thu, Sep 08, 2016 at 12:12:22PM +0100, Ian Jackson wrote:
> George Dunlap writes ("Re: Impact of HW vulnerabilities & Implications on Security Vulnerability Process"):
> > What's the conclusion here -- are you inclined to say that we shouldn't
> > issue an XSA, but perhaps do some other sort of announcement?
> 
> I would like us to _either_ issue an XSA or some other sort of
> announcement.
> 

+1 for some other sort of announcement.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-09-08 11:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:08 Impact of HW vulnerabilities & Implications on Security Vulnerability Process Lars Kurth
2016-09-07 15:33 ` Ian Jackson
2016-09-07 15:44   ` Jan Beulich
2016-09-07 15:59   ` George Dunlap
2016-09-07 16:05   ` George Dunlap
2016-09-08 11:12     ` Ian Jackson
2016-09-08 11:19       ` Wei Liu [this message]
2016-09-08 11:39       ` Lars Kurth
2016-09-07 19:08   ` Stefano Stabellini
2016-09-07 20:33     ` Meng Xu
2016-09-07 21:02       ` Stefano Stabellini
2016-09-07 21:31         ` Andrew Cooper
2016-09-07 22:01           ` Stefano Stabellini
2016-09-08  9:29         ` George Dunlap

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=20160908111937.GD12697@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=committers@xenproject.org \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=lars.kurth.xen@gmail.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).