From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH] x86: make IDT read-only Date: Tue, 09 Apr 2013 02:45:46 -0700 Message-ID: <877gkc596d.fsf@xmission.com> References: <20130408224328.GA17641@www.outflux.net> <51634935.9010905@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51634935.9010905@zytor.com> (H. Peter Anvin's message of "Mon, 08 Apr 2013 15:48:21 -0700") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: "H. Peter Anvin" Cc: Alexander Duyck , Alex Shi , Jeremy Fitzhardinge , Will Drewry , Kees Cook , Julien Tinnes , Konrad Rzeszutek Wilk , Frederic Weisbecker , Dan Rosenberg , x86@kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt , Borislav Petkov , Ingo Molnar , kernel-hardening@lists.openwall.com, Thomas Gleixner , "Paul E. McKenney" , virtualization@lists.linux-foundation.org, xen-devel@lists.xensource.com List-Id: virtualization@lists.linuxfoundation.org "H. Peter Anvin" writes: > On 04/08/2013 03:43 PM, Kees Cook wrote: >> This makes the IDT unconditionally read-only. This primarily removes >> the IDT from being a target for arbitrary memory write attacks. It has >> an added benefit of also not leaking (via the "sidt" instruction) the >> kernel base offset, if it has been relocated. >> >> Signed-off-by: Kees Cook >> Cc: Eric Northup > > Also, tglx: does this interfere with your per-cpu IDT efforts? Given that we don't change any IDT entries why would anyone want a per-cpu IDT? The cache lines should easily be shared accross all processors. Or are there some giant NUMA machines that trigger cache misses when accessing the IDT and the penalty for pulling the cache line across the NUMA fabric is prohibitive? Eric