From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/6] Patch 1
Date: Wed, 25 Apr 2018 23:39:57 -0400 [thread overview]
Message-ID: <e00d2eea-48dc-db63-630f-d9628cbe69e9@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1804251951090.20500@i7.lan>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On 04/25/2018 11:22 PM, speck for Linus Torvalds wrote:
> I don't know. Maybe I'm missing something. But it *already* sounds
> impossible to use in practice, and I pretty much guarantee that if you
> need terabytes of swap space in use on a desktop (and another 6-8 bits of
> physical addressing on the Xeons?) there is absolutely no way people will
> have swap offsets big enough to ever hit the MAX_PA/2 bit.
A bunch of us (including Amazon) discussed this limitation (MAX_PA/2)
and it seemed somewhat academic that you'd be able to pull off an attack
at that point reliably. There doesn't seem to be any downside to adding
a vulnerable warning in sysfs in that case, which was also suggested.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-04-26 3:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 3:29 [MODERATED] [PATCH 1/6] Patch 1 Andi Kleen
2018-04-25 15:51 ` [MODERATED] " Linus Torvalds
2018-04-25 16:06 ` Andi Kleen
2018-04-25 17:25 ` Linus Torvalds
2018-04-25 17:36 ` Andi Kleen
2018-04-25 18:00 ` Linus Torvalds
2018-04-25 18:11 ` Andi Kleen
2018-04-25 18:26 ` Thomas Gleixner
2018-04-25 18:30 ` [MODERATED] " Linus Torvalds
2018-04-25 18:51 ` Andi Kleen
2018-04-25 20:15 ` Linus Torvalds
2018-04-25 21:19 ` Andi Kleen
2018-04-25 22:35 ` Linus Torvalds
2018-04-25 23:12 ` Andi Kleen
2018-04-25 23:21 ` Linus Torvalds
2018-04-25 23:39 ` Andi Kleen
2018-04-26 3:22 ` Linus Torvalds
2018-04-26 3:39 ` Jon Masters [this message]
2018-04-26 13:59 ` Michal Hocko
2018-04-26 17:14 ` Linus Torvalds
2018-04-27 0:05 ` Andi Kleen
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=e00d2eea-48dc-db63-630f-d9628cbe69e9@redhat.com \
--to=jcm@redhat.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.