All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kees Cook <keescook@chromium.org>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	Ingo Molnar <mingo@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Alex Shi <alex.shi@intel.com>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Alexander Duyck <alexander.h.duyck@intel.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	Dan Rosenberg <drosenberg@vsecurity.com>,
	Julien Tinnes <jln@google.com>, Will Drewry <wad@chromium.org>,
	Eric Northup <digitaleric@google.com>
Subject: Re: [kernel-hardening] Re: [PATCH] x86: make IDT read-only
Date: Wed, 10 Apr 2013 11:52:12 +0200	[thread overview]
Message-ID: <20130410095212.GE24443@gmail.com> (raw)
In-Reply-To: <5164AC44.7030708@zytor.com>


* H. Peter Anvin <hpa@zytor.com> 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

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
	Alex Shi <alex.shi@intel.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Will Drewry <wad@chromium.org>, Kees Cook <keescook@chromium.org>,
	Julien Tinnes <jln@google.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Dan Rosenberg <drosenberg@vsecurity.com>,
	"x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Ingo Molnar <mingo@redhat.com>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [kernel-hardening] Re: [PATCH] x86: make IDT read-only
Date: Wed, 10 Apr 2013 11:52:12 +0200	[thread overview]
Message-ID: <20130410095212.GE24443@gmail.com> (raw)
In-Reply-To: <5164AC44.7030708@zytor.com>


* H. Peter Anvin <hpa@zytor.com> 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

  reply	other threads:[~2013-04-10  9:52 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 22:43 [kernel-hardening] [PATCH] x86: make IDT read-only Kees Cook
2013-04-08 22:43 ` Kees Cook
2013-04-08 22:43 ` Kees Cook
2013-04-08 22:47 ` [kernel-hardening] " H. Peter Anvin
2013-04-08 22:47   ` H. Peter Anvin
2013-04-08 22:47   ` H. Peter Anvin
2013-04-08 22:55   ` [kernel-hardening] " Kees Cook
2013-04-08 22:55     ` Kees Cook
2013-04-08 22:55     ` Kees Cook
2013-04-08 22:48 ` [kernel-hardening] " H. Peter Anvin
2013-04-08 22:48   ` H. Peter Anvin
2013-04-08 22:48   ` H. Peter Anvin
2013-04-09  9:23   ` Thomas Gleixner
2013-04-09  9:23   ` [kernel-hardening] " Thomas Gleixner
2013-04-09  9:23     ` Thomas Gleixner
2013-04-09 18:22     ` [kernel-hardening] " Kees Cook
2013-04-09 18:22       ` Kees Cook
2013-04-09 18:26       ` H. Peter Anvin
2013-04-09 18:26         ` H. Peter Anvin
2013-04-09 18:31         ` Kees Cook
2013-04-09 18:31           ` Kees Cook
2013-04-09 18:39           ` H. Peter Anvin
2013-04-09 18:39             ` H. Peter Anvin
2013-04-09 18:46             ` Kees Cook
2013-04-09 18:46               ` Kees Cook
2013-04-09 18:50               ` H. Peter Anvin
2013-04-09 18:50                 ` H. Peter Anvin
2013-04-09 18:53                 ` Kees Cook
2013-04-09 18:53                   ` Kees Cook
2013-04-09 18:54               ` Eric Northup
2013-04-09 18:54                 ` Eric Northup
2013-04-09 18:59                 ` H. Peter Anvin
2013-04-09 18:59                   ` H. Peter Anvin
2013-04-10  0:43                 ` [kernel-hardening] Readonly GDT H. Peter Anvin
2013-04-10  0:43                   ` H. Peter Anvin
2013-04-10  0:43                   ` H. Peter Anvin
2013-04-10  0:53                   ` [kernel-hardening] " Steven Rostedt
2013-04-10  0:53                     ` Steven Rostedt
2013-04-10  0:53                     ` Steven Rostedt
2013-04-10  0:58                     ` [kernel-hardening] " H. Peter Anvin
2013-04-10  0:58                       ` H. Peter Anvin
2013-04-10  0:58                       ` H. Peter Anvin
2013-04-10  9:42                   ` [kernel-hardening] Re: [Xen-devel] " Jan Beulich
2013-04-10  9:42                     ` Jan Beulich
2013-04-10  9:42                     ` Jan Beulich
2013-04-10 14:16                     ` [kernel-hardening] " H. Peter Anvin
2013-04-10 14:16                       ` H. Peter Anvin
2013-04-10 14:16                       ` H. Peter Anvin
2013-04-10 18:28                     ` [kernel-hardening] " H. Peter Anvin
2013-04-10 18:28                       ` H. Peter Anvin
2013-04-10  9:41               ` [kernel-hardening] Re: [PATCH] x86: make IDT read-only Ingo Molnar
2013-04-10  9:41                 ` Ingo Molnar
2013-04-10  0:03       ` H. Peter Anvin
2013-04-10  0:03         ` H. Peter Anvin
2013-04-10  9:52         ` Ingo Molnar [this message]
2013-04-10  9:52           ` Ingo Molnar
2013-04-09  9:45   ` Eric W. Biederman
2013-04-09  9:45     ` Eric W. Biederman
2013-04-09  9:45     ` Eric W. Biederman
2013-04-10  9:57     ` [kernel-hardening] " Ingo Molnar
2013-04-10  9:57       ` Ingo Molnar
2013-04-10  9:57       ` Ingo Molnar
2013-04-10 10:40       ` [kernel-hardening] " Eric W. Biederman
2013-04-10 10:40         ` Eric W. Biederman
2013-04-10 10:40         ` Eric W. Biederman
2013-04-10 16:31         ` [kernel-hardening] " Eric Northup
2013-04-10 16:31           ` Eric Northup
2013-04-10 16:31           ` Eric Northup
2013-04-10 16:48           ` [kernel-hardening] " H. Peter Anvin
2013-04-10 16:48             ` H. Peter Anvin
2013-04-10 16:48             ` H. Peter Anvin
2013-04-08 22:56 ` [kernel-hardening] " Maciej W. Rozycki
2013-04-08 22:56   ` Maciej W. Rozycki
2013-04-08 23:00   ` [kernel-hardening] " Kees Cook
2013-04-08 23:00     ` Kees Cook
2013-04-08 23:00     ` Kees Cook
2013-04-08 23:05   ` [kernel-hardening] " Kees Cook
2013-04-08 23:05     ` Kees Cook
2013-04-08 23:05     ` Kees Cook
2013-04-08 23:42     ` [kernel-hardening] " Maciej W. Rozycki
2013-04-08 23:42       ` Maciej W. Rozycki
2013-04-08 23:42       ` Maciej W. Rozycki
2013-04-08 22:56 ` Maciej W. Rozycki

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=20130410095212.GE24443@gmail.com \
    --to=mingo@kernel.org \
    --cc=alex.shi@intel.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=borislav.petkov@amd.com \
    --cc=digitaleric@google.com \
    --cc=drosenberg@vsecurity.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=jln@google.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wad@chromium.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.