From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751431AbdKUXRT (ORCPT ); Tue, 21 Nov 2017 18:17:19 -0500 Received: from mga14.intel.com ([192.55.52.115]:30446 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751290AbdKUXRS (ORCPT ); Tue, 21 Nov 2017 18:17:18 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,432,1505804400"; d="scan'208";a="8037734" Subject: Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables To: Andy Lutomirski References: <20171110193058.BECA7D88@viggo.jf.intel.com> <20171110193125.EBF58596@viggo.jf.intel.com> Cc: Andy Lutomirski , Thomas Gleixner , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , moritz.lipp@iaik.tugraz.at, Daniel Gruss , michael.schwarz@iaik.tugraz.at, richard.fellner@student.tugraz.at, Linus Torvalds , Kees Cook , Hugh Dickins , X86 ML From: Dave Hansen Message-ID: <02e48e97-5842-6a19-1ea2-cee4ed5910f4@linux.intel.com> Date: Tue, 21 Nov 2017 15:17:15 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/21/2017 02:46 PM, Andy Lutomirski wrote: >> GDT: R/O TSS: R/W at least because of trampoline stack entry code: >> EXEC+R/O exception stacks: R/W > Can you avoid code duplication by adding some logic right after the > kernel cpu_entry_area is set up to iterate page by page over the PTEs > in the cpu_entry_area for that CPU and just install exactly the same > PTEs into the kaiser table? E.g. just call kaiser_add_mapping once > per page but with the parameters read out from the fixmap PTEs > instead of hard coded? Yes, we could do that. But, what's the gain? We end up removing effectively three (long) lines of code from three kaiser_add_mapping() calls. To do this, we need to special-case the kernel page table walker to deal with PTEs only since we can't just grab PMD or PUD flags and stick them in a PTE. We would only be able to use this path when populating things that we know are 4k-mapped in the kernel. I guess the upside is that we don't open-code the permissions in the KAISER code that *have* to match the permissions that the kernel itself established. It also means that theoretically you could not touch the KAISER code the next time we expand the cpu entry area.