Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 5 Apr 2013 16:18:49 -0700
From: Kees Cook <>
To: Borislav Petkov <>, Julien Tinnes <>, Kees Cook <>, 
	LKML <>, 
	"" <>, "H. Peter Anvin" <>, 
	Thomas Gleixner <>, Ingo Molnar <>, "" <>, 
	Jarkko Sakkinen <>, Matthew Garrett <>, 
	Matt Fleming <>, Eric Northup <>, 
	Dan Rosenberg <>, Will Drewry <>
Subject: Re: [PATCH 3/3] x86: kernel base offset ASLR

On Fri, Apr 5, 2013 at 1:43 PM, Borislav Petkov <> wrote:
> On Fri, Apr 05, 2013 at 01:19:39PM -0700, Julien Tinnes wrote:
>> I think it'd be perfectly ok for OOPS to print out the kernel base.
> Yeah, ok, this still would need some massaging of the oops output per
> script, but it shouldn't be a big problem.
> Also, you probably need to make clear in the oops itself that the
> addresses have been randomized. Or, is the mere presence of kernel base
> going to imply that?

There is already a hook in the patch that prints the offset:

+dump_kernel_offset(struct notifier_block *self, unsigned long v, void *p)
+       pr_emerg("Kernel Offset: 0x%lx\n",
+                (unsigned long)&_text - __START_KERNEL);
+       atomic_notifier_chain_register(&panic_notifier_list,
+                                       &kernel_offset_notifier);

But of course, this can get improved.


Kees Cook
Chrome OS Security

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.