From: Dave Hansen <dave.hansen@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/1 v2] Linux patch #1
Date: Sat, 30 Jun 2018 16:34:15 -0700 [thread overview]
Message-ID: <a8556e53-d975-babc-6dd4-dc26be411fe8@linux.intel.com> (raw)
In-Reply-To: <20180630004130.GE17013@tassilo.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On 06/29/2018 05:41 PM, speck for Andi Kleen wrote:
> Two steps:
> - do you control the guest OS?
> - is the guest OS mitigated too.
>
> Then they are safe.
I'd say it another way: Do you depend on the security boundaries that
are established by hardware virtualization, but weakened by L1TF?
Let's be honest, it's a rather rare case that code that's run, even in
guests, is fully under your control. You might "trust" it, but if you
run a web browser in there, you shouldn't trust it farther than you can
throw it.
I can't tell you how many times I've heard folks say through this entire
Spectre/Meltdown/whatever fun that they are a closed system that does
not run untrusted code and they don't think they need mitigation. They
totally trust their web browser, app store and network daemons.
next prev parent reply other threads:[~2018-06-30 23:34 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 22:53 [MODERATED] [PATCH 1/1] Linux patch #1 Jiri Kosina
2018-06-28 23:15 ` [MODERATED] " Jiri Kosina
2018-06-28 23:36 ` [MODERATED] [PATCH 1/1 v2] " Jiri Kosina
2018-06-29 8:38 ` [MODERATED] " Borislav Petkov
2018-06-29 15:43 ` Thomas Gleixner
2018-06-29 15:46 ` Thomas Gleixner
2018-06-29 16:48 ` [MODERATED] " Josh Poimboeuf
2018-06-29 16:49 ` Josh Poimboeuf
2018-06-29 19:47 ` Thomas Gleixner
2018-06-29 19:54 ` [MODERATED] " Josh Poimboeuf
2018-06-29 21:26 ` Jiri Kosina
2018-06-29 21:28 ` Jiri Kosina
2018-06-29 22:05 ` Andi Kleen
2018-06-29 22:17 ` Jiri Kosina
2018-06-29 23:21 ` Andi Kleen
2018-06-29 23:33 ` Jiri Kosina
2018-06-29 23:37 ` Jiri Kosina
2018-06-29 23:44 ` Andi Kleen
2018-06-30 0:02 ` Jiri Kosina
2018-06-30 0:41 ` Andi Kleen
2018-06-30 0:50 ` Jiri Kosina
2018-06-30 8:59 ` Thomas Gleixner
2018-06-30 17:42 ` [MODERATED] " Linus Torvalds
2018-06-30 19:30 ` Jiri Kosina
2018-06-30 19:52 ` Linus Torvalds
2018-06-30 19:58 ` Jiri Kosina
2018-07-02 14:52 ` Konrad Rzeszutek Wilk
2018-07-02 8:06 ` Thomas Gleixner
2018-07-05 20:03 ` [MODERATED] " Jon Masters
2018-07-05 20:16 ` Jiri Kosina
2018-07-05 21:29 ` Jon Masters
2018-07-05 21:39 ` Jiri Kosina
2018-07-05 22:19 ` Thomas Gleixner
2018-07-05 23:49 ` [MODERATED] " Josh Poimboeuf
2018-07-05 20:25 ` Linus Torvalds
2018-07-05 20:50 ` Thomas Gleixner
2018-07-05 21:21 ` [MODERATED] " Jon Masters
2018-07-05 21:24 ` Jon Masters
2018-06-30 14:59 ` Josh Poimboeuf
2018-06-30 23:34 ` Dave Hansen [this message]
2018-07-01 0:06 ` Linus Torvalds
2018-06-29 21:46 ` Josh Poimboeuf
2018-06-29 21:49 ` Andi Kleen
2018-06-29 21:56 ` Jiri Kosina
2018-06-29 22:05 ` Thomas Gleixner
2018-06-29 22:43 ` [MODERATED] " Luck, Tony
2018-06-30 9:05 ` Thomas Gleixner
2018-06-30 19:48 ` [MODERATED] [PATCH 1/1 v3] " Jiri Kosina
2018-06-30 21:31 ` [MODERATED] " Josh Poimboeuf
2018-06-30 21:35 ` Linus Torvalds
2018-06-30 21:43 ` Jiri Kosina
2018-06-30 22:22 ` [MODERATED] [PATCH 1/1 v4] " Jiri Kosina
2018-07-02 14:51 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-07-02 15:00 ` Jiri Kosina
2018-07-02 15:14 ` Thomas Gleixner
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=a8556e53-d975-babc-6dd4-dc26be411fe8@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=speck@linutronix.de \
/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.