From: David Laight <David.Laight@ACULAB.COM>
To: "'Andy Lutomirski'" <luto@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Kees Cook <keescook@chromium.org>
Subject: RE: [PATCH] LDT improvements
Date: Fri, 8 Dec 2017 17:29:08 +0000 [thread overview]
Message-ID: <77ea98ade5ee40788c0a1b5d62b2d3e2@AcuMS.aculab.com> (raw)
In-Reply-To: <CALCETrWZhXgq9akoh5UXiTMbPXfw-9GSuV3CiTQan3Yr6WdiMQ@mail.gmail.com>
From: Andy Lutomirski
> Sent: 08 December 2017 16:48
...
> I mean: if the user CS or SS is not accessed and the LDT is RO, then
> we get #PF on the IRET instruction, I think. Dealing with that is
> truly awful.
Any fault in-kernel on the IRET is horrid.
Doesn't really matter which one.
Same goes for the 'pop %ds' (etc) that tend to precede it.
David
prev parent reply other threads:[~2017-12-08 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 7:22 Andy Lutomirski
2017-12-07 12:43 ` Borislav Petkov
2017-12-07 17:08 ` Andy Lutomirski
2017-12-07 17:23 ` Thomas Gleixner
2017-12-07 18:21 ` Andy Lutomirski
2017-12-08 7:34 ` Ingo Molnar
2017-12-08 9:34 ` Thomas Gleixner
2017-12-08 9:44 ` Ingo Molnar
2017-12-08 9:55 ` Thomas Gleixner
2017-12-08 11:31 ` Ingo Molnar
2017-12-08 16:38 ` Andy Lutomirski
2017-12-08 17:37 ` Thomas Gleixner
2017-12-08 17:42 ` Andy Lutomirski
2017-12-08 17:48 ` Peter Zijlstra
2017-12-08 13:20 ` Andy Lutomirski
2017-12-08 13:55 ` David Laight
2017-12-08 14:06 ` Peter Zijlstra
2017-12-08 16:20 ` Peter Zijlstra
2017-12-08 16:33 ` Andy Lutomirski
2017-12-08 16:46 ` David Laight
2017-12-08 16:47 ` Andy Lutomirski
2017-12-08 17:29 ` David Laight [this message]
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=77ea98ade5ee40788c0a1b5d62b2d3e2@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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