diff options
| author | Gary Ching-Pang Lin <glin@suse.com> | 2014-06-25 09:53:23 -0400 |
|---|---|---|
| committer | Peter Jones <pjones@redhat.com> | 2014-06-25 09:53:23 -0400 |
| commit | da49ac6d699f2a91bd088fc66ba31c42803ade3e (patch) | |
| tree | caf5413f6e742f65733958d7b509cecadd700ff5 /Cryptlib/OpenSSL/crypto/dsa/dsa_err.c | |
| parent | 8bf83b55dc252cc6b5b83bb0f33cdc8fb68c448b (diff) | |
| download | efi-boot-shim-da49ac6d699f2a91bd088fc66ba31c42803ade3e.tar.gz efi-boot-shim-da49ac6d699f2a91bd088fc66ba31c42803ade3e.zip | |
Fetch the netboot image from the same device
The previous strategy is to locate the first available PXE_BASE_CODE
protocol and to fetch the second stage image from it, and this may
cause shim to fetch the wrong second stage image, i.e. grub.efi.
Consider the machine with the following boot order:
1. PXE Boot
2. Hard Drive
Assume that the EFI image, e.g. bootx64.efi, in the PXE server is
broken, then "PXE Boot" will fail and fallback to "Hard Drive". While
shim.efi in "Hard Drive" is loaded, it will find the PXE protocol is
available and fetch grub.efi from the PXE server, not grub.efi in the
disk.
This commit checks the DeviceHandle from Loaded Image. If the device
supports PXE, then shim fetches grub.efi with the PXE protocol. Otherwise,
shim loads grub.efi from the disk.
Signed-off-by: Gary Ching-Pang Lin <glin@suse.com>
Diffstat (limited to 'Cryptlib/OpenSSL/crypto/dsa/dsa_err.c')
0 files changed, 0 insertions, 0 deletions