diff options
| author |   Ard Biesheuvel <ardb@kernel.org> | 2020-03-29 10:05:44 +0200 |
|---|---|---|
| committer |   Ingo Molnar <mingo@kernel.org> | 2020-03-29 12:08:18 +0200 |
| commit | 594e576d4b93b8cda3247542366b47e1b2ddc4dc (patch) | |
| tree | b90cf1010a424c0f007b3b953570a48113f124e3 /security | |
| parent | efi/libstub/arm64: Avoid image_base value from efi_loaded_image (diff) | |
| download | wireguard-linux-594e576d4b93b8cda3247542366b47e1b2ddc4dc.tar.xz wireguard-linux-594e576d4b93b8cda3247542366b47e1b2ddc4dc.zip | |
efi/libstub/arm: Fix spurious message that an initrd was loaded
Commit:
ec93fc371f014a6f ("efi/libstub: Add support for loading the initrd from a device path")
added a diagnostic print to the ARM version of the EFI stub that
reports whether an initrd has been loaded that was passed
via the command line using initrd=.
However, it failed to take into account that, for historical reasons,
the file loading routines return EFI_SUCCESS when no file was found,
and the only way to decide whether a file was loaded is to inspect
the 'size' argument that is passed by reference. So let's inspect
this returned size, to prevent the print from being emitted even if
no initrd was loaded at all.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-efi@vger.kernel.org
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions