2018-05-07 21:02:21 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0+
|
2017-09-13 22:05:38 +00:00
|
|
|
/*
|
2018-10-18 19:51:38 +00:00
|
|
|
* EFI boot manager
|
2017-09-13 22:05:38 +00:00
|
|
|
*
|
|
|
|
* Copyright (c) 2017 Rob Clark
|
|
|
|
*/
|
|
|
|
|
2020-05-31 08:07:31 +00:00
|
|
|
#define LOG_CATEGORY LOGC_EFI
|
|
|
|
|
2017-09-13 22:05:38 +00:00
|
|
|
#include <common.h>
|
|
|
|
#include <charset.h>
|
2020-05-10 17:40:05 +00:00
|
|
|
#include <log.h>
|
2017-09-13 22:05:38 +00:00
|
|
|
#include <malloc.h>
|
efi_loader: bootmgr: add booting from removable media
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot script for removable media").
This is, however, half-baked implementation because
1) UEFI specification requires this feature to be implemented as part
of Boot Manager's responsibility:
3 - Boot Manager
3.5.1 Boot via the Simple File Protocol
When booting via the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL, the FilePath will
start with a device path that points to the device that implements the
EFI_SIMPLE_FILE_SYSTEM_PROTOCOL or the EFI_BLOCK_IO_PROTOCOL. The next
part of the FilePath may point to the file name, including
subdirectories, which contain the bootable image. If the file name is
a null device path, the file name must be generated from the rules
defined below.
...
3.5.1.1 Removable Media Boot Behavior
To generate a file name when none is present in the FilePath, the
firmware must append a default file name in the form
\EFI\BOOT\BOOT{machine type short-name}.EFI ...
2) So (1) entails the hehavior that the user's preference of boot media
order should be determined by Boot#### and BootOrder variables.
With this patch, the semantics mentioned above is fully implemented.
For example, if you want to boot the system from USB and SCSI in this
order,
* define Boot0001 which contains only a device path to the USB device
(without any file path/name)
* define Boot0002 which contains only a device path to the SCSI device,
and
* set BootOrder to Boot0001:Boot0002
To avoid build error for sandbox, default file name "BOOTSANDBOX.efi"
is defined even if it is out of scope of UEFI specification.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
On sandbox use binary name corresponding to host architecture.
Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
2022-04-28 08:09:39 +00:00
|
|
|
#include <efi_default_filename.h>
|
2017-09-13 22:05:38 +00:00
|
|
|
#include <efi_loader.h>
|
2020-06-24 17:09:18 +00:00
|
|
|
#include <efi_variable.h>
|
2018-11-05 09:06:41 +00:00
|
|
|
#include <asm/unaligned.h>
|
2017-09-13 22:05:38 +00:00
|
|
|
|
|
|
|
static const struct efi_boot_services *bs;
|
|
|
|
static const struct efi_runtime_services *rs;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* bootmgr implements the logic of trying to find a payload to boot
|
|
|
|
* based on the BootOrder + BootXXXX variables, and then loading it.
|
|
|
|
*
|
|
|
|
* TODO detecting a special key held (f9?) and displaying a boot menu
|
|
|
|
* like you would get on a PC would be clever.
|
|
|
|
*
|
|
|
|
* TODO if we had a way to write and persist variables after the OS
|
|
|
|
* has started, we'd also want to check OsIndications to see if we
|
|
|
|
* should do normal or recovery boot.
|
|
|
|
*/
|
|
|
|
|
efi_loader: bootmgr: add booting from removable media
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot script for removable media").
This is, however, half-baked implementation because
1) UEFI specification requires this feature to be implemented as part
of Boot Manager's responsibility:
3 - Boot Manager
3.5.1 Boot via the Simple File Protocol
When booting via the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL, the FilePath will
start with a device path that points to the device that implements the
EFI_SIMPLE_FILE_SYSTEM_PROTOCOL or the EFI_BLOCK_IO_PROTOCOL. The next
part of the FilePath may point to the file name, including
subdirectories, which contain the bootable image. If the file name is
a null device path, the file name must be generated from the rules
defined below.
...
3.5.1.1 Removable Media Boot Behavior
To generate a file name when none is present in the FilePath, the
firmware must append a default file name in the form
\EFI\BOOT\BOOT{machine type short-name}.EFI ...
2) So (1) entails the hehavior that the user's preference of boot media
order should be determined by Boot#### and BootOrder variables.
With this patch, the semantics mentioned above is fully implemented.
For example, if you want to boot the system from USB and SCSI in this
order,
* define Boot0001 which contains only a device path to the USB device
(without any file path/name)
* define Boot0002 which contains only a device path to the SCSI device,
and
* set BootOrder to Boot0001:Boot0002
To avoid build error for sandbox, default file name "BOOTSANDBOX.efi"
is defined even if it is out of scope of UEFI specification.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
On sandbox use binary name corresponding to host architecture.
Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
2022-04-28 08:09:39 +00:00
|
|
|
/**
|
|
|
|
* expand_media_path() - expand a device path for default file name
|
|
|
|
* @device_path: device path to check against
|
|
|
|
*
|
|
|
|
* If @device_path is a media or disk partition which houses a file
|
|
|
|
* system, this function returns a full device path which contains
|
|
|
|
* an architecture-specific default file name for removable media.
|
|
|
|
*
|
|
|
|
* Return: a newly allocated device path
|
|
|
|
*/
|
|
|
|
static
|
|
|
|
struct efi_device_path *expand_media_path(struct efi_device_path *device_path)
|
|
|
|
{
|
2022-06-11 05:22:07 +00:00
|
|
|
struct efi_device_path *dp, *rem, *full_path;
|
efi_loader: bootmgr: add booting from removable media
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot script for removable media").
This is, however, half-baked implementation because
1) UEFI specification requires this feature to be implemented as part
of Boot Manager's responsibility:
3 - Boot Manager
3.5.1 Boot via the Simple File Protocol
When booting via the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL, the FilePath will
start with a device path that points to the device that implements the
EFI_SIMPLE_FILE_SYSTEM_PROTOCOL or the EFI_BLOCK_IO_PROTOCOL. The next
part of the FilePath may point to the file name, including
subdirectories, which contain the bootable image. If the file name is
a null device path, the file name must be generated from the rules
defined below.
...
3.5.1.1 Removable Media Boot Behavior
To generate a file name when none is present in the FilePath, the
firmware must append a default file name in the form
\EFI\BOOT\BOOT{machine type short-name}.EFI ...
2) So (1) entails the hehavior that the user's preference of boot media
order should be determined by Boot#### and BootOrder variables.
With this patch, the semantics mentioned above is fully implemented.
For example, if you want to boot the system from USB and SCSI in this
order,
* define Boot0001 which contains only a device path to the USB device
(without any file path/name)
* define Boot0002 which contains only a device path to the SCSI device,
and
* set BootOrder to Boot0001:Boot0002
To avoid build error for sandbox, default file name "BOOTSANDBOX.efi"
is defined even if it is out of scope of UEFI specification.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
On sandbox use binary name corresponding to host architecture.
Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
2022-04-28 08:09:39 +00:00
|
|
|
efi_handle_t handle;
|
|
|
|
|
|
|
|
if (!device_path)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If device_path is a (removable) media or partition which provides
|
|
|
|
* simple file system protocol, append a default file name to support
|
|
|
|
* booting from removable media.
|
|
|
|
*/
|
|
|
|
dp = device_path;
|
2022-06-11 05:22:07 +00:00
|
|
|
handle = efi_dp_find_obj(dp, &efi_simple_file_system_protocol_guid,
|
|
|
|
&rem);
|
2022-06-11 05:22:08 +00:00
|
|
|
if (handle) {
|
2022-06-11 05:22:07 +00:00
|
|
|
if (rem->type == DEVICE_PATH_TYPE_END) {
|
efi_loader: bootmgr: add booting from removable media
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot script for removable media").
This is, however, half-baked implementation because
1) UEFI specification requires this feature to be implemented as part
of Boot Manager's responsibility:
3 - Boot Manager
3.5.1 Boot via the Simple File Protocol
When booting via the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL, the FilePath will
start with a device path that points to the device that implements the
EFI_SIMPLE_FILE_SYSTEM_PROTOCOL or the EFI_BLOCK_IO_PROTOCOL. The next
part of the FilePath may point to the file name, including
subdirectories, which contain the bootable image. If the file name is
a null device path, the file name must be generated from the rules
defined below.
...
3.5.1.1 Removable Media Boot Behavior
To generate a file name when none is present in the FilePath, the
firmware must append a default file name in the form
\EFI\BOOT\BOOT{machine type short-name}.EFI ...
2) So (1) entails the hehavior that the user's preference of boot media
order should be determined by Boot#### and BootOrder variables.
With this patch, the semantics mentioned above is fully implemented.
For example, if you want to boot the system from USB and SCSI in this
order,
* define Boot0001 which contains only a device path to the USB device
(without any file path/name)
* define Boot0002 which contains only a device path to the SCSI device,
and
* set BootOrder to Boot0001:Boot0002
To avoid build error for sandbox, default file name "BOOTSANDBOX.efi"
is defined even if it is out of scope of UEFI specification.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
On sandbox use binary name corresponding to host architecture.
Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
2022-04-28 08:09:39 +00:00
|
|
|
dp = efi_dp_from_file(NULL, 0,
|
|
|
|
"/EFI/BOOT/" BOOTEFI_NAME);
|
|
|
|
full_path = efi_dp_append(device_path, dp);
|
|
|
|
efi_free_pool(dp);
|
|
|
|
} else {
|
|
|
|
full_path = efi_dp_dup(device_path);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
full_path = efi_dp_dup(device_path);
|
|
|
|
}
|
|
|
|
|
|
|
|
return full_path;
|
|
|
|
}
|
|
|
|
|
2022-05-12 02:29:02 +00:00
|
|
|
/**
|
|
|
|
* try_load_from_file_path() - try to load a file
|
|
|
|
*
|
|
|
|
* Given a file media path iterate through a list of handles and try to
|
|
|
|
* to load the file from each of them until the first success.
|
|
|
|
*
|
|
|
|
* @fs_handles: array of handles with the simple file protocol
|
|
|
|
* @num: number of handles in fs_handles
|
|
|
|
* @fp: file path to open
|
|
|
|
* @handle: on return pointer to handle for loaded image
|
|
|
|
* @removable: if true only consider removable media, else only non-removable
|
|
|
|
*/
|
|
|
|
static efi_status_t try_load_from_file_path(efi_handle_t *fs_handles,
|
|
|
|
efi_uintn_t num,
|
|
|
|
struct efi_device_path *fp,
|
|
|
|
efi_handle_t *handle,
|
|
|
|
bool removable)
|
|
|
|
{
|
|
|
|
struct efi_handler *handler;
|
|
|
|
struct efi_device_path *dp;
|
|
|
|
int i;
|
|
|
|
efi_status_t ret;
|
|
|
|
|
|
|
|
for (i = 0; i < num; i++) {
|
|
|
|
if (removable != efi_disk_is_removable(fs_handles[i]))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
ret = efi_search_protocol(fs_handles[i], &efi_guid_device_path,
|
|
|
|
&handler);
|
|
|
|
if (ret != EFI_SUCCESS)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
dp = handler->protocol_interface;
|
|
|
|
if (!dp)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
dp = efi_dp_append(dp, fp);
|
|
|
|
if (!dp)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
ret = EFI_CALL(efi_load_image(true, efi_root, dp, NULL, 0,
|
|
|
|
handle));
|
|
|
|
efi_free_pool(dp);
|
|
|
|
if (ret == EFI_SUCCESS)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
return EFI_NOT_FOUND;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* try_load_from_short_path
|
|
|
|
* @fp: file path
|
|
|
|
* @handle: pointer to handle for newly installed image
|
|
|
|
*
|
|
|
|
* Enumerate all the devices which support file system operations,
|
|
|
|
* prepend its media device path to the file path, @fp, and
|
|
|
|
* try to load the file.
|
|
|
|
* This function should be called when handling a short-form path
|
|
|
|
* which is starting with a file device path.
|
|
|
|
*
|
|
|
|
* Return: status code
|
|
|
|
*/
|
|
|
|
static efi_status_t try_load_from_short_path(struct efi_device_path *fp,
|
|
|
|
efi_handle_t *handle)
|
|
|
|
{
|
|
|
|
efi_handle_t *fs_handles;
|
|
|
|
efi_uintn_t num;
|
|
|
|
efi_status_t ret;
|
|
|
|
|
|
|
|
ret = EFI_CALL(efi_locate_handle_buffer(
|
|
|
|
BY_PROTOCOL,
|
|
|
|
&efi_simple_file_system_protocol_guid,
|
|
|
|
NULL,
|
|
|
|
&num, &fs_handles));
|
|
|
|
if (ret != EFI_SUCCESS)
|
|
|
|
return ret;
|
|
|
|
if (!num)
|
|
|
|
return EFI_NOT_FOUND;
|
|
|
|
|
|
|
|
/* removable media first */
|
|
|
|
ret = try_load_from_file_path(fs_handles, num, fp, handle, true);
|
|
|
|
if (ret == EFI_SUCCESS)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
/* fixed media */
|
|
|
|
ret = try_load_from_file_path(fs_handles, num, fp, handle, false);
|
|
|
|
if (ret == EFI_SUCCESS)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
out:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2019-07-14 11:20:28 +00:00
|
|
|
/**
|
|
|
|
* try_load_entry() - try to load image for boot option
|
|
|
|
*
|
2017-09-13 22:05:38 +00:00
|
|
|
* Attempt to load load-option number 'n', returning device_path and file_path
|
2019-07-14 11:20:28 +00:00
|
|
|
* if successful. This checks that the EFI_LOAD_OPTION is active (enabled)
|
2017-09-13 22:05:38 +00:00
|
|
|
* and that the specified file to boot exists.
|
2019-07-14 11:20:28 +00:00
|
|
|
*
|
2020-08-07 15:49:39 +00:00
|
|
|
* @n: number of the boot option, e.g. 0x0a13 for Boot0A13
|
|
|
|
* @handle: on return handle for the newly installed image
|
|
|
|
* @load_options: load options set on the loaded image protocol
|
|
|
|
* Return: status code
|
2017-09-13 22:05:38 +00:00
|
|
|
*/
|
2020-08-07 15:49:39 +00:00
|
|
|
static efi_status_t try_load_entry(u16 n, efi_handle_t *handle,
|
|
|
|
void **load_options)
|
2017-09-13 22:05:38 +00:00
|
|
|
{
|
2018-11-05 09:06:41 +00:00
|
|
|
struct efi_load_option lo;
|
2022-04-25 21:35:01 +00:00
|
|
|
u16 varname[9];
|
2019-04-19 03:22:35 +00:00
|
|
|
void *load_option;
|
2018-05-17 05:57:05 +00:00
|
|
|
efi_uintn_t size;
|
2019-04-19 03:22:35 +00:00
|
|
|
efi_status_t ret;
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2022-04-25 21:35:01 +00:00
|
|
|
efi_create_indexed_name(varname, sizeof(varname), "Boot", n);
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2021-03-27 08:56:07 +00:00
|
|
|
load_option = efi_get_var(varname, &efi_global_variable_guid, &size);
|
2017-09-13 22:05:38 +00:00
|
|
|
if (!load_option)
|
2019-04-19 03:22:35 +00:00
|
|
|
return EFI_LOAD_ERROR;
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2020-05-31 20:46:09 +00:00
|
|
|
ret = efi_deserialize_load_option(&lo, load_option, &size);
|
|
|
|
if (ret != EFI_SUCCESS) {
|
|
|
|
log_warning("Invalid load option for %ls\n", varname);
|
|
|
|
goto error;
|
|
|
|
}
|
2017-09-13 22:05:38 +00:00
|
|
|
|
|
|
|
if (lo.attributes & LOAD_OPTION_ACTIVE) {
|
efi_loader: bootmgr: add booting from removable media
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot script for removable media").
This is, however, half-baked implementation because
1) UEFI specification requires this feature to be implemented as part
of Boot Manager's responsibility:
3 - Boot Manager
3.5.1 Boot via the Simple File Protocol
When booting via the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL, the FilePath will
start with a device path that points to the device that implements the
EFI_SIMPLE_FILE_SYSTEM_PROTOCOL or the EFI_BLOCK_IO_PROTOCOL. The next
part of the FilePath may point to the file name, including
subdirectories, which contain the bootable image. If the file name is
a null device path, the file name must be generated from the rules
defined below.
...
3.5.1.1 Removable Media Boot Behavior
To generate a file name when none is present in the FilePath, the
firmware must append a default file name in the form
\EFI\BOOT\BOOT{machine type short-name}.EFI ...
2) So (1) entails the hehavior that the user's preference of boot media
order should be determined by Boot#### and BootOrder variables.
With this patch, the semantics mentioned above is fully implemented.
For example, if you want to boot the system from USB and SCSI in this
order,
* define Boot0001 which contains only a device path to the USB device
(without any file path/name)
* define Boot0002 which contains only a device path to the SCSI device,
and
* set BootOrder to Boot0001:Boot0002
To avoid build error for sandbox, default file name "BOOTSANDBOX.efi"
is defined even if it is out of scope of UEFI specification.
Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
On sandbox use binary name corresponding to host architecture.
Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
2022-04-28 08:09:39 +00:00
|
|
|
struct efi_device_path *file_path;
|
2019-03-20 00:07:55 +00:00
|
|
|
u32 attributes;
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2022-04-29 05:15:04 +00:00
|
|
|
log_debug("trying to load \"%ls\" from %pD\n", lo.label,
|
|
|
|
lo.file_path);
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2022-05-12 02:29:02 +00:00
|
|
|
if (EFI_DP_TYPE(lo.file_path, MEDIA_DEVICE, FILE_PATH)) {
|
|
|
|
/* file_path doesn't contain a device path */
|
|
|
|
ret = try_load_from_short_path(lo.file_path, handle);
|
|
|
|
} else {
|
|
|
|
file_path = expand_media_path(lo.file_path);
|
|
|
|
ret = EFI_CALL(efi_load_image(true, efi_root, file_path,
|
|
|
|
NULL, 0, handle));
|
|
|
|
efi_free_pool(file_path);
|
|
|
|
}
|
2019-05-29 18:54:25 +00:00
|
|
|
if (ret != EFI_SUCCESS) {
|
2020-05-31 08:07:31 +00:00
|
|
|
log_warning("Loading %ls '%ls' failed\n",
|
|
|
|
varname, lo.label);
|
2017-09-13 22:05:38 +00:00
|
|
|
goto error;
|
2019-05-29 18:54:25 +00:00
|
|
|
}
|
2017-09-13 22:05:38 +00:00
|
|
|
|
2019-03-20 00:07:55 +00:00
|
|
|
attributes = EFI_VARIABLE_BOOTSERVICE_ACCESS |
|
|
|
|
EFI_VARIABLE_RUNTIME_ACCESS;
|
2022-01-23 19:55:12 +00:00
|
|
|
ret = efi_set_variable_int(u"BootCurrent",
|
2020-06-24 17:09:18 +00:00
|
|
|
&efi_global_variable_guid,
|
2020-08-07 15:49:39 +00:00
|
|
|
attributes, sizeof(n), &n, false);
|
2021-03-17 19:55:00 +00:00
|
|
|
if (ret != EFI_SUCCESS)
|
|
|
|
goto unload;
|
|
|
|
/* try to register load file2 for initrd's */
|
|
|
|
if (IS_ENABLED(CONFIG_EFI_LOAD_FILE2_INITRD)) {
|
|
|
|
ret = efi_initrd_register();
|
|
|
|
if (ret != EFI_SUCCESS)
|
|
|
|
goto unload;
|
2019-04-19 03:22:35 +00:00
|
|
|
}
|
2019-03-20 00:07:55 +00:00
|
|
|
|
2020-05-31 08:07:31 +00:00
|
|
|
log_info("Booting: %ls\n", lo.label);
|
2019-04-19 03:22:35 +00:00
|
|
|
} else {
|
|
|
|
ret = EFI_LOAD_ERROR;
|
2017-09-13 22:05:38 +00:00
|
|
|
}
|
|
|
|
|
2020-08-07 15:49:39 +00:00
|
|
|
/* Set load options */
|
|
|
|
if (size) {
|
|
|
|
*load_options = malloc(size);
|
|
|
|
if (!*load_options) {
|
|
|
|
ret = EFI_OUT_OF_RESOURCES;
|
|
|
|
goto error;
|
|
|
|
}
|
|
|
|
memcpy(*load_options, lo.optional_data, size);
|
|
|
|
ret = efi_set_load_options(*handle, size, *load_options);
|
|
|
|
} else {
|
2020-12-27 14:46:00 +00:00
|
|
|
*load_options = NULL;
|
2020-08-07 15:49:39 +00:00
|
|
|
}
|
|
|
|
|
2017-09-13 22:05:38 +00:00
|
|
|
error:
|
|
|
|
free(load_option);
|
|
|
|
|
2021-03-17 19:55:00 +00:00
|
|
|
return ret;
|
|
|
|
|
|
|
|
unload:
|
|
|
|
if (EFI_CALL(efi_unload_image(*handle)) != EFI_SUCCESS)
|
|
|
|
log_err("Unloading image failed\n");
|
|
|
|
free(load_option);
|
|
|
|
|
2019-04-19 03:22:35 +00:00
|
|
|
return ret;
|
2017-09-13 22:05:38 +00:00
|
|
|
}
|
|
|
|
|
2019-07-14 11:20:28 +00:00
|
|
|
/**
|
|
|
|
* efi_bootmgr_load() - try to load from BootNext or BootOrder
|
|
|
|
*
|
2019-03-20 00:07:55 +00:00
|
|
|
* Attempt to load from BootNext or in the order specified by BootOrder
|
|
|
|
* EFI variable, the available load-options, finding and returning
|
|
|
|
* the first one that can be loaded successfully.
|
2019-07-14 11:20:28 +00:00
|
|
|
*
|
2020-08-07 15:49:39 +00:00
|
|
|
* @handle: on return handle for the newly installed image
|
|
|
|
* @load_options: load options set on the loaded image protocol
|
|
|
|
* Return: status code
|
2017-09-13 22:05:38 +00:00
|
|
|
*/
|
2020-08-07 15:49:39 +00:00
|
|
|
efi_status_t efi_bootmgr_load(efi_handle_t *handle, void **load_options)
|
2017-09-13 22:05:38 +00:00
|
|
|
{
|
2019-03-20 00:07:55 +00:00
|
|
|
u16 bootnext, *bootorder;
|
2018-05-17 05:57:05 +00:00
|
|
|
efi_uintn_t size;
|
2017-09-13 22:05:38 +00:00
|
|
|
int i, num;
|
2019-03-20 00:07:55 +00:00
|
|
|
efi_status_t ret;
|
2017-09-13 22:05:38 +00:00
|
|
|
|
|
|
|
bs = systab.boottime;
|
|
|
|
rs = systab.runtime;
|
|
|
|
|
2019-03-20 00:07:55 +00:00
|
|
|
/* BootNext */
|
|
|
|
size = sizeof(bootnext);
|
2022-01-23 19:55:12 +00:00
|
|
|
ret = efi_get_variable_int(u"BootNext",
|
2020-06-24 17:09:18 +00:00
|
|
|
&efi_global_variable_guid,
|
|
|
|
NULL, &size, &bootnext, NULL);
|
2019-03-20 00:07:55 +00:00
|
|
|
if (ret == EFI_SUCCESS || ret == EFI_BUFFER_TOO_SMALL) {
|
|
|
|
/* BootNext does exist here */
|
|
|
|
if (ret == EFI_BUFFER_TOO_SMALL || size != sizeof(u16))
|
2020-05-31 08:07:31 +00:00
|
|
|
log_err("BootNext must be 16-bit integer\n");
|
2019-03-20 00:07:55 +00:00
|
|
|
|
|
|
|
/* delete BootNext */
|
2022-01-23 19:55:12 +00:00
|
|
|
ret = efi_set_variable_int(u"BootNext",
|
2020-06-24 17:09:18 +00:00
|
|
|
&efi_global_variable_guid,
|
|
|
|
0, 0, NULL, false);
|
2019-03-20 00:07:55 +00:00
|
|
|
|
|
|
|
/* load BootNext */
|
|
|
|
if (ret == EFI_SUCCESS) {
|
|
|
|
if (size == sizeof(u16)) {
|
2020-08-07 15:49:39 +00:00
|
|
|
ret = try_load_entry(bootnext, handle,
|
|
|
|
load_options);
|
2019-04-19 03:22:35 +00:00
|
|
|
if (ret == EFI_SUCCESS)
|
|
|
|
return ret;
|
2020-05-31 08:07:31 +00:00
|
|
|
log_warning(
|
|
|
|
"Loading from BootNext failed, falling back to BootOrder\n");
|
2019-03-20 00:07:55 +00:00
|
|
|
}
|
|
|
|
} else {
|
2020-05-31 08:07:31 +00:00
|
|
|
log_err("Deleting BootNext failed\n");
|
2019-03-20 00:07:55 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* BootOrder */
|
2022-01-23 19:55:12 +00:00
|
|
|
bootorder = efi_get_var(u"BootOrder", &efi_global_variable_guid, &size);
|
2019-02-24 03:44:48 +00:00
|
|
|
if (!bootorder) {
|
2020-05-31 08:07:31 +00:00
|
|
|
log_info("BootOrder not defined\n");
|
2019-04-19 03:22:35 +00:00
|
|
|
ret = EFI_NOT_FOUND;
|
2017-09-13 22:05:38 +00:00
|
|
|
goto error;
|
2019-02-24 03:44:48 +00:00
|
|
|
}
|
2017-09-13 22:05:38 +00:00
|
|
|
|
|
|
|
num = size / sizeof(uint16_t);
|
|
|
|
for (i = 0; i < num; i++) {
|
2022-04-29 05:15:04 +00:00
|
|
|
log_debug("trying to load Boot%04X\n", bootorder[i]);
|
2020-08-07 15:49:39 +00:00
|
|
|
ret = try_load_entry(bootorder[i], handle, load_options);
|
2019-04-19 03:22:35 +00:00
|
|
|
if (ret == EFI_SUCCESS)
|
2017-09-13 22:05:38 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
free(bootorder);
|
|
|
|
|
|
|
|
error:
|
2019-04-19 03:22:35 +00:00
|
|
|
return ret;
|
2017-09-13 22:05:38 +00:00
|
|
|
}
|