Skip to contentSkip to conversation

efi/libstub: add initial Boot Loader Interface support

PATCH In review Vincent Mailhol 2 participants 4 messages Sep 6 – Sep 9 EFI

lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 efi/libstub: add initial Boot Loader Interface support

The Boot Loader Interface (BLI) [1] defines EFI variables that expose boot loader state to the running OS. LoaderInfo identifies the boot loader, while LoaderDevicePartUUID records the GPT partition UUID of the partition containing it.

LoaderDevicePartUUID is used, for example, by systemd-gpt-auto-generator
[2] to identify the disk the boot loader was launched from and automatically detect and mount partitions on it.

GRUB [3] and systemd-boot [4] populate these variables, but when the kernel is started directly by EFI firmware, there is no conventional external boot loader to provide them. In that case, because the EFI stub performs the boot loader role, it should provide the variables itself.

Use LoaderInfo as a sentinel: if it is already set by an earlier boot stage or cannot be set, bail out. Otherwise, populate the other BLI variables.

Parse the loaded image device path, extract the GUID signature from its GPT HD() node and publish it under the Linux loader entry vendor GUID as the volatile LoaderDevicePartUUID EFI variable.

Install the efi_bli_set_variables() hook in both the generic efi-stub.c path and the x86-specific x86-stub.c path.

[1] The Boot Loader Interface

[2] systemd-gpt-auto-generator

[3] GRUB -- §16.2 bli

[4] systemd -- systemd-boot UEFI Boot Manager

---
Changes in v3:

- Populate LoaderInfo in addition to LoaderDevicePartUUID.

- Use LoaderInfo as the provider-level sentinel before setting BLI variables.

- Drop CONFIG_EFI_STUB_BLI and enable the feature unconditionally.

- Use the libstub %pUl formatter instead of local GUID string conversion.

- Mode type definitions to efi.h and add enums for the EFI HD() partition format and signature type fields.

- Reintroduce the NULL check on image to resolve the sashiko finding:

    https://sashiko.dev/#/patchset/20260903-efi_stub_bli-v2-1-dbf7ba915117%40kernel.org

- Link to v2: https://patch.msgid.link/[email protected]

Changes in v2:

- Add CONFIG_EFI_STUB_BLI to make the BLI feature optional.

- Use static storage for GUID initializers. This reduces the size by about 10% compared to v1.

- Remove the redundant NULL check on image.

- Move the nibble-to-ASCII-hex conversion out of efi_bli_guid_to_str() into the new efi_bli_nibble_to_hex().

- Rename variables to be closer to the EFI specification.

Link to v1: https://lore.kernel.org/r/[email protected]
---
This patch depends on series "efi/libstub: Avoid UTF-16 conversion busywork" from Ard.

Bloat-o-meter results on drivers/firmware/efi/libstub/lib.a before and after this patch on x86_64 with gcc 15.3.0:

add/remove: 4/0 grow/shrink: 1/0 up/down: 770/0 (770)
Function old new delta

  efi_bli_set_variables                          -     636    +636
  loader_info                                    -      90     +90
  loader_entry_guid                              -      16     +16
  device_path_guid                               -      16     +16
  efi_stub_entry                              4180    4192     +12
  Total: Before=29436, After=30206, chg +2.62%
---
 drivers/firmware/efi/libstub/Makefile   |  2 +-
 drivers/firmware/efi/libstub/bli.c      | 87 +++++++++++++++++++++++++++++++++
 drivers/firmware/efi/libstub/efi-stub.c |  1 +
 drivers/firmware/efi/libstub/efistub.h  |  2 +
 drivers/firmware/efi/libstub/x86-stub.c |  1 +
 include/linux/efi.h                     | 22 +++++++++
 6 files changed, 114 insertions(+), 1 deletion(-)
drivers/firmware/efi/libstub/Makefile +1 -1
index 12c0c7deb5cb..c3cb0779b2ce 100644
@@ -63,7 +63,7 @@ KBUILD_CFLAGS_KERNEL := $(filter-out -fdata-sections, $(KBUILD_CFLAGS_KERNEL))
 
 KBUILD_AFLAGS			:= $(KBUILD_CFLAGS) -D__ASSEMBLY__
 
-lib-y				:= efi-stub-helper.o gop.o secureboot.o tpm.o \
+lib-y				:= bli.o efi-stub-helper.o gop.o secureboot.o tpm.o \
 				   file.o mem.o random.o randomalloc.o pci.o \
 				   skip_spaces.o lib-cmdline.o lib-ctype.o \
 				   alignedmem.o printk.o vsprintf.o \
drivers/firmware/efi/libstub/bli.c new file +87 -0

87 lines not on this page · raw message

drivers/firmware/efi/libstub/efi-stub.c +1 -0
index 42d6073bcd06..2a95f4ea104a 100644
@@ -165,6 +165,7 @@ efi_status_t efi_stub_common(efi_handle_t handle,
 	dpy = setup_primary_display();
 
 	efi_retrieve_eventlog();
+	efi_bli_set_variables(image);
 
 	/* Ask the firmware to clear memory on unclean shutdown */
 	efi_enable_reset_attack_mitigation();
drivers/firmware/efi/libstub/efistub.h +2 -0
index 880c1d0c464b..2dbcb8157c95 100644
@@ -1072,6 +1072,8 @@ efi_status_t efi_random_alloc(unsigned long size, unsigned long align,
 			      int memory_type, unsigned long alloc_min,
 			      unsigned long alloc_max);
 
+void efi_bli_set_variables(efi_loaded_image_t *image);
+
 efi_status_t efi_random_get_seed(void);
 
 efi_status_t check_platform_features(void);
drivers/firmware/efi/libstub/x86-stub.c +1 -0
index cef32e2c82d8..b762f7f37f28 100644
@@ -1014,6 +1014,7 @@ void __noreturn efi_stub_entry(efi_handle_t handle,
 	efi_random_get_seed();
 
 	efi_retrieve_eventlog();
+	efi_bli_set_variables(image);
 
 	setup_graphics(boot_params);
 
include/linux/efi.h +22 -0
index c35446a0b66f..ecb34be37a87 100644
@@ -957,6 +957,17 @@ extern int efi_status_to_err(efi_status_t status);
 #define   EFI_DEV_END_INSTANCE			0x01
 #define   EFI_DEV_END_ENTIRE			0xFF
 
+enum efi_hd_partition_format {
+	EFI_HD_PARTITION_FORMAT_MBR = 1,
+	EFI_HD_PARTITION_FORMAT_GPT,
+};
+
+enum efi_hd_signature_type {
+	EFI_HD_SIGNATURE_TYPE_NONE,
+	EFI_HD_SIGNATURE_TYPE_MBR,
+	EFI_HD_SIGNATURE_TYPE_GUID,
+};
+
 struct efi_generic_dev_path {
 	u8				type;
 	u8				sub_type;
@@ -988,6 +999,16 @@ struct efi_rel_offset_dev_path {
 	u64				ending_offset;
 } __packed;
 
+struct efi_hd_dev_path {
+	struct efi_generic_dev_path	header;
+	u32				partition_number;
+	u64				partition_start;
+	u64				partition_size;
+	efi_guid_t			signature;
+	u8				partition_format;
+	u8				signature_type;
+} __packed;
+
 struct efi_mem_mapped_dev_path {
 	struct efi_generic_dev_path	header;
 	u32				memory_type;
@@ -1007,6 +1028,7 @@ struct efi_dev_path {
 		struct efi_pci_dev_path		pci;
 		struct efi_vendor_dev_path	vendor;
 		struct efi_rel_offset_dev_path	rel_offset;
+		struct efi_hd_dev_path		hd;
 	};
 } __packed;
 

---
base-commit: 7046b0d50cf479b4122a5b0ab2f03ac07cd0de22
change-id: 20260724-efi_stub_bli-477289050225

Best regards,

Signature · 1 line
Vincent Mailhol <[email protected]>
maintainer Reviewed-by on v3 1/1
#1 lore raw

Hi Vincent,

Quoted 91 lines · Vincent Mailhol

The Boot Loader Interface (BLI) [1] defines EFI variables that expose boot loader state to the running OS. LoaderInfo identifies the boot loader, while LoaderDevicePartUUID records the GPT partition UUID of the partition containing it.

LoaderDevicePartUUID is used, for example, by systemd-gpt-auto-generator
[2] to identify the disk the boot loader was launched from and automatically detect and mount partitions on it.

GRUB [3] and systemd-boot [4] populate these variables, but when the kernel is started directly by EFI firmware, there is no conventional external boot loader to provide them. In that case, because the EFI stub performs the boot loader role, it should provide the variables itself.

Use LoaderInfo as a sentinel: if it is already set by an earlier boot stage or cannot be set, bail out. Otherwise, populate the other BLI variables.

Parse the loaded image device path, extract the GUID signature from its GPT HD() node and publish it under the Linux loader entry vendor GUID as the volatile LoaderDevicePartUUID EFI variable.

Install the efi_bli_set_variables() hook in both the generic efi-stub.c path and the x86-specific x86-stub.c path.

[1] The Boot Loader Interface

[2] systemd-gpt-auto-generator
Link:
https://www.freedesktop.org/software/systemd/man/latest/systemd-gpt-auto-generator.html

[3] GRUB -- §16.2 bli
Link:
https://www.gnu.org/software/grub/manual/grub/html_node/bli_005fmodule.html

[4] systemd -- systemd-boot UEFI Boot Manager

---
Changes in v3:

- Populate LoaderInfo in addition to LoaderDevicePartUUID.

- Use LoaderInfo as the provider-level sentinel before setting BLI variables.

- Drop CONFIG_EFI_STUB_BLI and enable the feature unconditionally.

- Use the libstub %pUl formatter instead of local GUID string conversion.

- Mode type definitions to efi.h and add enums for the EFI HD() partition format and signature type fields.

- Reintroduce the NULL check on image to resolve the sashiko finding:

https://sashiko.dev/#/patchset/20260903-efi_stub_bli-v2-1-dbf7ba915117%40kernel.org

- Link to v2:
https://patch.msgid.link/[email protected]

Changes in v2:

- Add CONFIG_EFI_STUB_BLI to make the BLI feature optional.

- Use static storage for GUID initializers. This reduces the size by about 10% compared to v1.

- Remove the redundant NULL check on image.

- Move the nibble-to-ASCII-hex conversion out of efi_bli_guid_to_str() into the new efi_bli_nibble_to_hex().

- Rename variables to be closer to the EFI specification.

Link to v1:
https://lore.kernel.org/r/[email protected]
---
This patch depends on series "efi/libstub: Avoid UTF-16 conversion busywork" from Ard.

Link:
https://lore.kernel.org/all/[email protected]/
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-libstub-native-utf16

Bloat-o-meter results on drivers/firmware/efi/libstub/lib.a before and after this patch on x86_64 with gcc 15.3.0:

add/remove: 4/0 grow/shrink: 1/0 up/down: 770/0 (770)
Function old new delta

Quoted 15 lines
  efi_bli_set_variables                          -     636    +636
  loader_info                                    -      90     +90
  loader_entry_guid                              -      16     +16
  device_path_guid                               -      16     +16
  efi_stub_entry                              4180    4192     +12
  Total: Before=29436, After=30206, chg +2.62%
---
 drivers/firmware/efi/libstub/Makefile   |  2 +-
 drivers/firmware/efi/libstub/bli.c      | 87 +++++++++++++++++++++++++++++++++
 drivers/firmware/efi/libstub/efi-stub.c |  1 +
 drivers/firmware/efi/libstub/efistub.h  |  2 +
 drivers/firmware/efi/libstub/x86-stub.c |  1 +
 include/linux/efi.h                     | 22 +++++++++
 6 files changed, 114 insertions(+), 1 deletion(-)

I'll pick this up once the prerequisites are in place.

#2 lore raw
In reply to Vincent Mailhol
Quoted 39 lines · Vincent Mailhol

The Boot Loader Interface (BLI) [1] defines EFI variables that expose boot loader state to the running OS. LoaderInfo identifies the boot loader, while LoaderDevicePartUUID records the GPT partition UUID of the partition containing it.

LoaderDevicePartUUID is used, for example, by systemd-gpt-auto-generator
[2] to identify the disk the boot loader was launched from and automatically detect and mount partitions on it.

GRUB [3] and systemd-boot [4] populate these variables, but when the kernel is started directly by EFI firmware, there is no conventional external boot loader to provide them. In that case, because the EFI stub performs the boot loader role, it should provide the variables itself.

Use LoaderInfo as a sentinel: if it is already set by an earlier boot stage or cannot be set, bail out. Otherwise, populate the other BLI variables.

Parse the loaded image device path, extract the GUID signature from its GPT HD() node and publish it under the Linux loader entry vendor GUID as the volatile LoaderDevicePartUUID EFI variable.

Install the efi_bli_set_variables() hook in both the generic efi-stub.c path and the x86-specific x86-stub.c path.

[1] The Boot Loader Interface

[2] systemd-gpt-auto-generator

[3] GRUB -- §16.2 bli

[4] systemd -- systemd-boot UEFI Boot Manager

---

(...)

Quoted 7 lines
drivers/firmware/efi/libstub/bli.c new file +7 -0
+static void efi_bli_populate_loader_part_uuid(efi_loaded_image_t *image)
+{
+	static efi_guid_t device_path_guid = EFI_DEVICE_PATH_PROTOCOL_GUID;
+	efi_char16_t partuuid[UUID_STRING_LEN + 1];
+	const struct efi_hd_dev_path *hd_node;
+	const struct efi_dev_path *path;
+

drivers/firmware/efi/libstub/bli.c line 61

Quoted 10 lines
drivers/firmware/efi/libstub/bli.c new file +10 -0
+	if (efi_bs_call(handle_protocol, efi_table_attr(image, device_handle),
+			&device_path_guid, (void **)&path) != EFI_SUCCESS)
+		return;
+
+	hd_node = efi_bli_find_hd_node(path);
+	if (!hd_node)
+		return;
+
+	if (efi_snprintf(partuuid, ARRAY_SIZE(partuuid), "%pUl",
+			 hd_node->signature.b) != UUID_STRING_LEN)
                         ^^^^^^^^^^^^^^^^^^^^

I just realize that there is a small mistake here. Conceptually speaking, %pUl expects a pointer to a efi_guid_t. Of course, because of the function being variadic, no type enforcement is done and the compiler is happy with hd_node->signature.b which is an u8 array.

But the clean approach is definitely:

	if (efi_snprintf(partuuid, ARRAY_SIZE(partuuid), "%pUl",
			 &hd_node->signature) != UUID_STRING_LEN)

@Ard, do you want me to send a v4, or can you just fix while applying?

drivers/firmware/efi/libstub/bli.c line 67

Quoted 6 lines
drivers/firmware/efi/libstub/bli.c new file +6 -0
+		return;
+
+	set_efi_var(L"LoaderDevicePartUUID", &loader_entry_guid,
+		    EFI_VARIABLE_BOOTSERVICE_ACCESS | EFI_VARIABLE_RUNTIME_ACCESS,
+		    sizeof(partuuid), partuuid);
+}

(...)

Yours sincerely,
Vincent Mailhol

maintainer
#3 lore raw
Quoted 66 lines · Vincent Mailhol
Quoted 39 lines · Vincent Mailhol

The Boot Loader Interface (BLI) [1] defines EFI variables that expose boot loader state to the running OS. LoaderInfo identifies the boot loader, while LoaderDevicePartUUID records the GPT partition UUID of the partition containing it.

LoaderDevicePartUUID is used, for example, by systemd-gpt-auto-generator
[2] to identify the disk the boot loader was launched from and automatically detect and mount partitions on it.

GRUB [3] and systemd-boot [4] populate these variables, but when the kernel is started directly by EFI firmware, there is no conventional external boot loader to provide them. In that case, because the EFI stub performs the boot loader role, it should provide the variables itself.

Use LoaderInfo as a sentinel: if it is already set by an earlier boot stage or cannot be set, bail out. Otherwise, populate the other BLI variables.

Parse the loaded image device path, extract the GUID signature from its GPT HD() node and publish it under the Linux loader entry vendor GUID as the volatile LoaderDevicePartUUID EFI variable.

Install the efi_bli_set_variables() hook in both the generic efi-stub.c path and the x86-specific x86-stub.c path.

[1] The Boot Loader Interface

[2] systemd-gpt-auto-generator

[3] GRUB -- §16.2 bli

[4] systemd -- systemd-boot UEFI Boot Manager

---

(...)

Quoted 7 lines
drivers/firmware/efi/libstub/bli.c new file +7 -0
+static void efi_bli_populate_loader_part_uuid(efi_loaded_image_t *image)
+{
+	static efi_guid_t device_path_guid = EFI_DEVICE_PATH_PROTOCOL_GUID;
+	efi_char16_t partuuid[UUID_STRING_LEN + 1];
+	const struct efi_hd_dev_path *hd_node;
+	const struct efi_dev_path *path;
+

drivers/firmware/efi/libstub/bli.c line 61

Quoted 10 lines
drivers/firmware/efi/libstub/bli.c new file +10 -0
+	if (efi_bs_call(handle_protocol, efi_table_attr(image, device_handle),
+			&device_path_guid, (void **)&path) != EFI_SUCCESS)
+		return;
+
+	hd_node = efi_bli_find_hd_node(path);
+	if (!hd_node)
+		return;
+
+	if (efi_snprintf(partuuid, ARRAY_SIZE(partuuid), "%pUl",
+			 hd_node->signature.b) != UUID_STRING_LEN)
                         ^^^^^^^^^^^^^^^^^^^^

I just realize that there is a small mistake here. Conceptually speaking, %pUl expects a pointer to a efi_guid_t. Of course, because of the function being variadic, no type enforcement is done and the compiler is happy with hd_node->signature.b which is an u8 array.

Quoted 7 lines

But the clean approach is definitely:

	if (efi_snprintf(partuuid, ARRAY_SIZE(partuuid), "%pUl",
			 &hd_node->signature) != UUID_STRING_LEN)

@Ard, do you want me to send a v4, or can you just fix while applying?

I'll fix that up.

Quoted 12 lines

drivers/firmware/efi/libstub/bli.c line 67

Quoted 6 lines
drivers/firmware/efi/libstub/bli.c new file +6 -0
+		return;
+
+	set_efi_var(L"LoaderDevicePartUUID", &loader_entry_guid,
+		    EFI_VARIABLE_BOOTSERVICE_ACCESS | EFI_VARIABLE_RUNTIME_ACCESS,
+		    sizeof(partuuid), partuuid);
+}

(...)

Yours sincerely,
Vincent Mailhol