From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Brian Gerst <brgerst@gmail.com>,
David Laight <David.Laight@aculab.com>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] LDT improvements
Date: Thu, 7 Dec 2017 13:43:47 +0100 [thread overview]
Message-ID: <20171207124347.p7kdj7q4qqs3ivri@pd.tnic> (raw)
In-Reply-To: <48fe5cf1382d6a95c7b1837415882edcc81a9781.1512631324.git.luto@kernel.org>
On Wed, Dec 06, 2017 at 11:22:21PM -0800, Andy Lutomirski wrote:
> I think I like this approach. I also think it might be nice to move the
> whole cpu_entry_area into this new pgd range so that we can stop mucking
> around with the fixmap.
Yeah, and also, I don't like the idea of sacrificing a whole PGD
only for the LDT crap which is optional, even. Frankly - and this
is just me - I'd make CONFIG_KERNEL_PAGE_TABLE_ISOLATION xor
CONFIG_MODIFY_LDT_SYSCALL and don't give a rat's *ss about the LDT.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-12-07 12:44 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 [this message]
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
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=20171207124347.p7kdj7q4qqs3ivri@pd.tnic \
--to=bp@alien8.de \
--cc=David.Laight@aculab.com \
--cc=brgerst@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®