efi_driver: don't bind internal block devices
authorHeinrich Schuchardt <heinrich.schuchardt@canonical.com>
Fri, 9 Sep 2022 06:57:58 +0000 (06:57 +0000)
committerHeinrich Schuchardt <heinrich.schuchardt@canonical.com>
Fri, 9 Sep 2022 14:07:54 +0000 (16:07 +0200)
commit8cf8ad353345cc4a92288b5136e7d714d2bdde4a
tree30f243512e466e8675f08ffbfa374e37065c13f6
parent793254893954dc96437b5b5541aab84485bf78b1
efi_driver: don't bind internal block devices

UEFI block devices can either mirror U-Boot's internal devices or be
provided by an EFI application like iPXE.

When ConnectController() is invoked for the EFI_BLOCK_IO_PROTOCOL
interface for such an application provided device we create a virtual
U-Boot block device of type "efi_blk".

Currently we do not call ConnectController() when handles for U-Boot's
internal block devices are created. If an EFI application calls
ConnectController() for a handle relating to an internal block device,
we erroneously create an extra "efi_blk" block device.

E.g. the UEFI shell has a command 'connect -r' which calls
ConnectController() for all handles with device path protocol.

In the Supported() method of our EFI_DRIVER_BINDING_PROTOCOL return
EFI_UNSUPPORTED when dealing with an U-Boot internal device.

Reported-by: Etienne Carriere <etienne.carriere@linaro.org>
Fixes: commit 05ef48a2484b ("efi_driver: EFI block driver")
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>
Tested-by: Etienne Carriere <etienne.carriere@linaro.org>
Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
lib/efi_driver/efi_uclass.c