From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/6] Patch 1
Date: Wed, 25 Apr 2018 09:06:54 -0700 [thread overview]
Message-ID: <20180425160654.GH14273@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1804250841450.19245@i7.lan>
On Wed, Apr 25, 2018 at 08:51:09AM -0700, speck for Linus Torvalds wrote:
>
>
> On Tue, 24 Apr 2018, speck for Andi Kleen wrote:
> >
> > This patch addresses the second case. The page is swapped out and
> > the PTE has been replaced with a swap entry. It could also
> > contain a migration or poison entry, which have the same format.
>
> NAK NAK NAK.
>
> Why is this doing the idiotic __swp_stop_mask, when I told multiple people
> not to do that, and when I've already seen the patch (from Michal Hocko?)
> that did the much simpler approach of unconditionally just inverting all
> the 'offset' bits.
We looked at it, but your invert approach is broken if there is any MMIO
space between MAX_PA/2 ... MAX_PA that is ever mapped to ring 3.
And we cannot rule that out.
In this case the inverted bit would start pointing to valid memory,
so everything would become attackable.
So yes the more complicated patches are needed.
-Andi
next prev parent reply other threads:[~2018-04-25 16:07 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 [this message]
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
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=20180425160654.GH14273@tassilo.jf.intel.com \
--to=ak@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.