From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754929AbdEDPr4 (ORCPT ); Thu, 4 May 2017 11:47:56 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:35255 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753182AbdEDPrU (ORCPT ); Thu, 4 May 2017 11:47:20 -0400 Date: Thu, 4 May 2017 08:47:17 -0700 From: Christoph Hellwig To: Daniel Gruss Cc: kernel list , kernel-hardening@lists.openwall.com, "clementine.maurice@iaik.tugraz.at" , "moritz.lipp@iaik.tugraz.at" , Michael Schwarz , Richard Fellner , kirill.shutemov@linux.intel.com, Ingo Molnar , "anders.fogh@gdata-adan.de" Subject: Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Message-ID: <20170504154717.GA24353@infradead.org> References: <9df77051-ac01-bfe9-3cf7-4c2ecbcb9292@iaik.tugraz.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9df77051-ac01-bfe9-3cf7-4c2ecbcb9292@iaik.tugraz.at> User-Agent: Mutt/1.8.0 (2017-02-23) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 4 May 2017 08:47:17 -0700 From: Christoph Hellwig Message-ID: <20170504154717.GA24353@infradead.org> References: <9df77051-ac01-bfe9-3cf7-4c2ecbcb9292@iaik.tugraz.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9df77051-ac01-bfe9-3cf7-4c2ecbcb9292@iaik.tugraz.at> Subject: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode To: Daniel Gruss Cc: kernel list , kernel-hardening@lists.openwall.com, "clementine.maurice@iaik.tugraz.at" , "moritz.lipp@iaik.tugraz.at" , Michael Schwarz , Richard Fellner , kirill.shutemov@linux.intel.com, Ingo Molnar , "anders.fogh@gdata-adan.de" List-ID: 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?