linux-kernel - Re: [x86, kaslr] BUG: kernel boot hang

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <CAGXu5jJLarLeYef0eEfEuVS4pDJf_3my-5BV1O6RX+LP7=hUag@mail.gmail.com>
Date:	Tue, 14 Jan 2014 15:31:43 -0800
From:	Kees Cook <keescook@...omium.org>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [x86, kaslr] BUG: kernel boot hang

On Tue, Jan 14, 2014 at 3:23 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
> On 01/14/2014 02:33 PM, Kees Cook wrote:
>>
>> Can you tell me how the initrd for quantal-core-x86_64.cgz was built
>> in the qemu instances you're using? It seems like all the failures
>> point to a problem with how kASLR is interacting with the initrd.
>>
>
> If kASLR somehow causes the kernel to collide with the initrd that would
> be problem...

Agreed, but I can't reproduce this yet. The initrd is on the list of
areas that get avoided, so the fundamental design isn't broken, but
clearly something is busted.

How long has tip:x86/kaslr been sitting in linux-next? If this is some
interaction between kaslr and something else, perhaps merge order just
happens to be pointing at kaslr?

Regardless, all my tests so far against next-20140114 and an initramfs
haven't seen corruption (using the given .config). I don't have the
same initrd, though, so I'm hoping getting that will trigger the
glitch.

-Kees

-- 
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/