Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S935189Ab3DHL63 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 8 Apr 2013 07:58:29 -0400
Received: from mail-bk0-f50.google.com ([209.85.214.50]:61979 "EHLO
	mail-bk0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S934591Ab3DHL62 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 8 Apr 2013 07:58:28 -0400
Date: Mon, 8 Apr 2013 13:58:23 +0200
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org,
        kernel-hardening@lists.openwall.com,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        x86@kernel.org, Jarkko Sakkinen <jarkko.sakkinen@intel.com>,
        Matthew Garrett <mjg@redhat.com>,
        Matt Fleming <matt.fleming@intel.com>,
        Eric Northup <digitaleric@google.com>,
        Dan Rosenberg <drosenberg@vsecurity.com>,
        Julien Tinnes <jln@google.com>, Will Drewry <wad@chromium.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 3/3] x86: kernel base offset ASLR
Message-ID: <20130408115823.GC7513@gmail.com>
References: <1365106055-22939-1-git-send-email-keescook@chromium.org>
 <1365106055-22939-4-git-send-email-keescook@chromium.org>
 <515DE0C9.3030709@zytor.com>
 <20130405080418.GG26889@gmail.com>
 <515EEE25.1030402@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <515EEE25.1030402@zytor.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 864
Lines: 26


* H. Peter Anvin <hpa@zytor.com> wrote:

> On 04/05/2013 01:04 AM, Ingo Molnar wrote:
> > 
> > Random runtime shuffling of the kernel image - is that possible with 
> > existing toolchains?
> > 
> 
> Yes... the question is how much work we'd be willing to go through to make it 
> happen.
> 
> One approach: the kernel already contains a linker -- used for modules -- and 
> the bulk of the kernel could actually be composed to a "pile of modules" that 
> gets linked on boot.  This would provide very large amounts of randomness.

Is there no code generation / micro-performance disadvantage to that?

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/