From: Christoph Hellwig <hch@infradead.org>
To: Daniel Gruss <daniel.gruss@iaik.tugraz.at>
Cc: kernel list <linux-kernel@vger.kernel.org>,
kernel-hardening@lists.openwall.com,
"clementine.maurice@iaik.tugraz.at"
<clementine.maurice@iaik.tugraz.at>,
"moritz.lipp@iaik.tugraz.at" <moritz.lipp@iaik.tugraz.at>,
Michael Schwarz <michael.schwarz@iaik.tugraz.at>,
Richard Fellner <richard.fellner@student.tugraz.at>,
kirill.shutemov@linux.intel.com, Ingo Molnar <mingo@kernel.org>,
"anders.fogh@gdata-adan.de" <anders.fogh@gdata-adan.de>
Subject: Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode
Date: Thu, 4 May 2017 08:47:17 -0700 [thread overview]
Message-ID: <20170504154717.GA24353@infradead.org> (raw)
In-Reply-To: <9df77051-ac01-bfe9-3cf7-4c2ecbcb9292@iaik.tugraz.at>
On Thu, May 04, 2017 at 12:02:47PM +0200, Daniel Gruss wrote:
> After several recent works [1,2,3] KASLR on x86_64 was basically considered
> dead by many researchers. We have been working on an efficient but effective
> fix for this problem and found that not mapping the kernel space when
> running in user mode is the solution to this problem [4] (the corresponding
> paper [5] will be presented at ESSoS17).
I'll try to read the paper. In the meantime: how different is your
approach from then one here?
https://lwn.net/Articles/39283/
and how different is the performance impact?
next prev parent reply other threads:[~2017-05-04 15:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 10:02 [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss
2017-05-04 12:26 ` Daniel Gruss
2017-05-04 15:28 ` [kernel-hardening] " Thomas Garnier
2017-05-05 8:23 ` Daniel Gruss
2017-05-05 15:47 ` Thomas Garnier
2017-05-06 4:02 ` David Gens
2017-05-06 8:38 ` Daniel Gruss
2017-05-08 10:21 ` Mark Rutland
2017-05-08 10:51 ` Daniel Gruss
2017-05-08 13:22 ` Mark Rutland
2017-05-08 13:43 ` Daniel Gruss
2017-05-08 13:53 ` Daniel Gruss
2017-05-08 14:09 ` Thomas Garnier
2017-05-08 14:19 ` Daniel Gruss
2017-05-08 13:23 ` Daniel Gruss
2017-05-04 15:47 ` Christoph Hellwig [this message]
2017-05-05 7:40 ` Daniel Gruss
2017-05-07 20:20 ` [kernel-hardening] " Richard Weinberger
2017-05-07 21:45 ` Daniel Gruss
2017-05-07 22:02 ` Richard Weinberger
2017-05-07 22:18 ` Daniel Gruss
2017-05-09 14:44 ` [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not mapkernel " Fogh, Anders
2017-05-09 14:57 ` Richard Weinberger
2017-05-09 15:30 ` Rik van Riel
2017-10-31 23:28 ` Dave Hansen
2017-05-05 15:49 ` [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel " Jann Horn
2017-05-05 15:53 ` Jann Horn
2017-05-06 8:28 ` Daniel Gruss
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=20170504154717.GA24353@infradead.org \
--to=hch@infradead.org \
--cc=anders.fogh@gdata-adan.de \
--cc=clementine.maurice@iaik.tugraz.at \
--cc=daniel.gruss@iaik.tugraz.at \
--cc=kernel-hardening@lists.openwall.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.schwarz@iaik.tugraz.at \
--cc=mingo@kernel.org \
--cc=moritz.lipp@iaik.tugraz.at \
--cc=richard.fellner@student.tugraz.at \
/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