linux-kernel - Re: Loading initrd above 4G causes freeze on boot

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]

Date:	Sun, 24 Aug 2014 22:19:04 +0300
From:	Mantas Mikulėnas <grawity@...il.com>
To:	Harald Hoyer <harald@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-efi@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: Loading initrd above 4G causes freeze on boot

On Fri, Aug 22, 2014 at 5:43 PM, Mantas Mikulėnas <grawity@...il.com> wrote:
>
> On Fri, Aug 22, 2014 at 5:24 PM, Harald Hoyer <harald@...hat.com> wrote:
> > On 09.08.2014 16:23, Mantas Mikulėnas wrote:
> >> As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> >> the kernel freezes at the earliest possible moment when trying to boot
> >> via UEFI on my Asus laptop. (It still boots via BIOS.)
> >>
> >> If I revert that commit on current master (c309bfa9b481), it boots
> >> correctly again [although I see "setup_efi_pci() failed" being printed].
> >>
> >> (Seems like it freezes when handle_cmdline_files() attempts to read
> >> the last chunk of the initramfs -- the last call to efi_file_read()
> >> never returns. Figuring out why that happens is beyond me, though.)
> >>
> >
> > I fixed my issue with: https://lkml.org/lkml/2014/8/22/232
>
> ...Well. If that's the _physical_ address, then I suppose it wouldn't
> have worked on my 4 GB laptop either way. (I thought UEFI already used
> some sort of virtual memory, so I never even thought to mention
> this... Oh well.)
>
> Though if that's the case, then I'm wondering why it would be affected
> by the read size? Shouldn't it have crashed either as soon as the high
> address was used, or never at all? (I really don't know much about
> memory at this level. Sorry.)
>
> > Care to test?
>
> Will try later today.

Finally got around to testing it, and yes, your patch fixes the initrd
boot for me.

-- 
Mantas Mikulėnas <grawity@...il.com>
--
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/