From: Jan Beulich <jbeulich@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen Security Advisory 360 v1 - IRQ vector leak on x86
Date: Thu, 21 Jan 2021 15:31:25 +0100 [thread overview]
Message-ID: <aa7839c8-de5c-14bb-5392-d8ee47ae1017@suse.com> (raw)
In-Reply-To: <20210121142012.GB1592@mail-itl>
On 21.01.2021 15:20, Marek Marczykowski-Górecki wrote:
> On Thu, Jan 21, 2021 at 02:10:48PM +0000, Xen.org security team wrote:
>> MITIGATION
>> ==========
>>
>> Not running HVM guests with PCI pass through devices will avoid the
>> vulnerability. Note that even non-malicious guests can trigger this
>> vulnerability as part of normal operation.
>
> Does the 'on_reboot="destroy"' mitigate the issue too? Or on_soft_reset?
I don't think so, no.
Jan
next prev parent reply other threads:[~2021-01-21 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 14:10 Xen Security Advisory 360 v1 - IRQ vector leak on x86 Xen.org security team
2021-01-21 14:20 ` Marek Marczykowski-Górecki
2021-01-21 14:31 ` Jan Beulich [this message]
2021-01-21 14:34 ` Roger Pau Monné
2021-01-21 14:50 ` Jan Beulich
2021-01-21 15:05 ` Roger Pau Monné
2021-01-21 15:09 ` Jan Beulich
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=aa7839c8-de5c-14bb-5392-d8ee47ae1017@suse.com \
--to=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.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).