From: Juergen Gross <jgross@suse.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@suse.de>,
Mike Latimer <mlatimer@suse.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/pti: don't report XenPV as vulnerable
Date: Mon, 18 Jun 2018 10:07:49 +0200 [thread overview]
Message-ID: <457f3e13-12e6-ed2f-5165-e413801a2172@suse.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1806180959080.6203@cbobk.fhfr.pm>
On 18/06/18 09:59, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.cz>
>
> Xen PV domain kernel is not by design affected by meltdown as it's
> enforcing split CR3 itself. Let's not report such systems as "Vulnerable"
> in sysfs (we're also already forcing PTI to off in X86_HYPER_XEN_PV
> cases); the security of the system ultimately depends on presence of
> mitigation in Hypervisor, which can't be easily detected from DomU; let's
> report that.
>
> Reported-and-tested-by: Mike Latimer <mlatimer@suse.com>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2018-06-18 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 22:32 [PATCH] " Jiri Kosina
2018-06-15 5:46 ` Juergen Gross
2018-06-15 6:04 ` Jiri Kosina
2018-06-15 6:10 ` Juergen Gross
2018-06-15 6:16 ` Jiri Kosina
2018-06-15 6:30 ` Juergen Gross
2018-06-15 6:39 ` Jiri Kosina
2018-06-15 7:00 ` Juergen Gross
2018-06-15 21:10 ` Jiri Kosina
2018-06-16 6:36 ` Juergen Gross
2018-06-18 7:59 ` [PATCH v2] " Jiri Kosina
2018-06-18 8:07 ` Juergen Gross [this message]
2018-06-19 8:02 ` [tip:x86/pti] x86/pti: Don't " tip-bot for Jiri Kosina
2018-06-21 12:24 ` tip-bot for Jiri Kosina
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=457f3e13-12e6-ed2f-5165-e413801a2172@suse.com \
--to=jgross@suse.com \
--cc=bp@suse.de \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlatimer@suse.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome