linux-kernel - eboot.c regression allows boot, from v3.7 on- no boot with UEFI, only legacy, bisect results

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-next>] [day] [month] [year] [list]

Message-ID: <CAEigmK-pY+9XF4V-KRZrbiO8GY5Fs6scE+Ehm1zc5T8V2RiB9g@mail.gmail.com>
Date:	Fri, 28 Mar 2014 16:08:36 -0400
From:	Daniel McLellan <daniel.mclellan@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	matt.fleming@...el.com, mjg@...hat.com
Subject: eboot.c regression allows boot, from v3.7 on- no boot with UEFI, only
 legacy, bisect results

System: Hewlett-Packard product: HP EliteBook 2570p
CPU~Dual core Intel Core i7-3520M CPU (-HT-MCP-)
Kernel: 3.12.4-2-hplove x86_64 (64 bit) Desktop: Enlightenment 0.18.99.18202
Distro: Arch Linux


I believe this issue is common to only a few iterations of ivy bridge

https://bbs.archlinux.org/viewtopic.php?id=156670
https://bugs.archlinux.org/task/33745?project=1

I had been patching eboot.c to v3.7 with the attached
efi_hp_boot.patch, but due to the recent changes in eboot.c (in v3.13)
I decided to bisect, and identified the following:

# first bad commit: [dd5fc854de5fd37adfcef8a366cd21a55aa01d3d] EFI:
Stash ROMs if they're not in the PCI BAR

My next step is diffing the eboot.c from v3.13.

or would a better path be to check for ivy bridge?
--
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/