Re: [PATCH] efi: payload: don't fail postcore initcall when image has no device path

[Sascha Hauer <s.hauer@pengutronix.de>]

On Wed, 26 Aug 2026 14:15:05 +0200, Ahmad Fatoum wrote:
> When barebox was loaded from memory or from a device without a device
> path, e.g. via QEMU's fw_cfg on top of the barebox EFI loader, the loaded
> image has no device handle. efi_postcore_init() currently bails out with
> -EINVAL in that case, printing an initcall error and skipping the
> registration of the barebox update handler.
> 
> There is no partition UUID to export as LoaderDevicePartUUID then, but
> that's no reason to abort the initcall. The parent image handle may lack a
> device path as well, and device_path_to_filepath() would then crash on the
> NULL pointer. Make device_path_next_compatible_node() tolerate a NULL
> device path, so both helpers just return NULL and the initcall proceeds
> with the defaults.
> 
> [...]

Applied, thanks!

[1/1] efi: payload: don't fail postcore initcall when image has no device path
      https://git.pengutronix.de/cgit/barebox/commit/?id=da47299449f3 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>