lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Mar 2014 12:58:06 -0700
From:	Kees Cook <>
To:	Andrew Morton <>
Cc:	Rusty Russell <>,
	Linus Torvalds <>,
	Andrew Honig <>,
	Michal Marek <>,
	"" <>, Tejun Heo <>,
	Tony Luck <>,
	Fenghua Yu <>,,
	LKML <>
Subject: Re: [PATCH v2 0/2] kallsyms: handle special absolute symbols

On Mon, Mar 10, 2014 at 12:06 PM, Andrew Morton
<> wrote:
> On Fri,  7 Mar 2014 17:00:23 -0800 Kees Cook <> wrote:
>> Handles 0-based per_cpu variables as being absolute so they are
>> not relocated under kASLR on x86_64.
> Would it be prudent to revert 0f55159d091cb1e5 ("kallsyms: fix absolute
> addresses for kASLR") then sort all this out for 3.15?

My opinion is that if it breaks a real-life case (avr32), it should be
reverted. The only people affected by the kallsyms per_cpu relocation
reporting bug are those using kASLR on x86, and even then the bug is a
corner case on live kernel debugging.

I am fine either way.


Kees Cook
Chrome OS Security
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists