Remove EFI support
efivars: itialize variable Introduced a few commits ago.
efivars: use greedy_realloc
efivars: use more _cleanup_ Also rename r to buf, since r is customarily reserved for the return value.
efivars: do binary and before converting to bool I'm pretty sure that this is what was meant here.
efivars: rename last remaining err to r
efivars: modernization Fix return value if unlink fails.
tree-wide: use _packed_ macro instead of raw gcc __attribute__
remove unused includes This patch removes includes that are not used. The removals were found with include-what-you-use which checks if any of the symbols from a header is in use.
bootctl: add sd-boot support
fix a couple of more lazy "return -1" Fix should strictly follow the rule to return negative errno-style error codes from functions, hence let's fix more "return -1"-style lazinesses.
gpt-auto-generator: automatically find the root disk of the system When run in an initrd and no root= argument is set (or is set to root=gpt-auto) we will automatically look for the root partition on the same disk the EFI ESP is located on. Since we look for swap, /home and /srv on the disk the root partition is located on, we hence have a fully discoverable chain: Firmware discovers the EFI ESP partition → the initrd discovers the root partition → the host OS discovers swap, /home, and /srv. Note that this requires an EFI boot loader that sets the LoaderDevicePartUUID EFI variable, such as Gummiboot.
make gcc shut up If -flto is used then gcc will generate a lot more warnings than before, among them a number of use-without-initialization warnings. Most of them without are false positives, but let's make them go away, because it doesn't really matter.
Modernization Fixes minor leak in error path in device.c.
Never call qsort on potentially NULL arrays This extends 62678ded 'efi: never call qsort on potentially NULL arrays' to all other places where qsort is used and it is not obvious that the count is non-zero.
efi: never call qsort on potentially NULL arrays
support acpi firmware performance data (FPDT) Prefer firmware-provided performance data over loader-exported ones; if ACPI data is available, always use it, otherwise try to read the loader data. The firmware-provided variables start at the time the first EFI image is executed and end when the operating system exits the boot services; the (loader) time calculated in systemd-analyze increases.
efivars: un-leak a few strings
efivars: fix return code Was returning 1 on read error.
bootctl: print secure boot flags