linux-kernel - Re: 3.12 to 3.13 boot regression bisected

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: <20140805135130.2d180b69@pluto>
Date:	Tue, 5 Aug 2014 13:51:30 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	P J P <ppandit@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org
Subject: Re: 3.12 to 3.13 boot regression bisected - still applies to 3.16

On Tue, 5 Aug 2014 10:18:48 +0100 Matt Fleming wrote:
> On Tue, 05 Aug, at 11:13:30AM, Bruno Prémont wrote:
> > 
> > I get at least to just before
> >   status = efi_call_early(exit_boot_services, handle, key);
> > in eboot.c on line 1310. A efi_printk inserted there is displayed.
> 
> This is worth pointing out in case you're unaware, but do you know that
> it's not valid to call efi_printk() after ExitBootServices()? Doing so
> will almost certainly cause your machine to fault.

I am aware that efi_printk() uses boot services!


Now I tried out loops at many places and have gotten up to line 340 in

  arch/x86/kernel/head_64.S

System reboots within the following assembler instructions (does not
reach line 359).

So efi_main() returns successfully but the assembler code following it
gets something wrong.

I'm going to try further to determine which line between 340 and 359 is
the "bad" one.

Bruno
--
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/