Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936703Ab3DJJwS (ORCPT ); Wed, 10 Apr 2013 05:52:18 -0400 Received: from mail-ee0-f54.google.com ([74.125.83.54]:36645 "EHLO mail-ee0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752845Ab3DJJwR (ORCPT ); Wed, 10 Apr 2013 05:52:17 -0400 Date: Wed, 10 Apr 2013 11:52:12 +0200 From: Ingo Molnar To: "H. Peter Anvin" Cc: Kees Cook , "kernel-hardening@lists.openwall.com" , Ingo Molnar , LKML , "x86@kernel.org" , Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , Marcelo Tosatti , Alex Shi , Borislav Petkov , Alexander Duyck , Frederic Weisbecker , Steven Rostedt , "Paul E. McKenney" , "xen-devel@lists.xensource.com" , "virtualization@lists.linux-foundation.org" , Dan Rosenberg , Julien Tinnes , Will Drewry , Eric Northup Subject: Re: [kernel-hardening] Re: [PATCH] x86: make IDT read-only Message-ID: <20130410095212.GE24443@gmail.com> References: <20130408224328.GA17641@www.outflux.net> <51634935.9010905@zytor.com> <5164AC44.7030708@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5164AC44.7030708@zytor.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 786 Lines: 26 * H. Peter Anvin wrote: > On 04/09/2013 11:22 AM, Kees Cook wrote: > > > > Can we create a RO fixed per-cpu area? > > > > "Fixed" and "percpu" are mutually exclusive... There's a fixmap area that holds kmap_atomic() percpu mappings: FIX_KMAP_BEGIN, /* reserved pte's for temporary kernel mappings */ FIX_KMAP_END = FIX_KMAP_BEGIN+(KM_TYPE_NR*NR_CPUS)-1, In a similar fashion we could use a per CPU high-mapped read-only alias as well (assuming it fits, memory is pretty tight there). Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/