public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "Liu, Zhiguang" <zhiguang.liu@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
	"Wu, Hao A" <hao.a.wu@intel.com>,
	"Gao, Zhichao" <zhichao.gao@intel.com>
Subject: Re: [PATCH] MdeModulePkg: Fix device path when the boot manager menu is from different FV
Date: Wed, 9 Jun 2021 09:50:01 +0000	[thread overview]
Message-ID: <CO1PR11MB49305A0B5DC7314118E02FA28C369@CO1PR11MB4930.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210609093708.2450-1-zhiguang.liu@intel.com>

Reviewed-by: Ray Ni <ray.ni@intel.com>

> -----Original Message-----
> From: Liu, Zhiguang <zhiguang.liu@intel.com>
> Sent: Wednesday, June 9, 2021 5:37 PM
> To: devel@edk2.groups.io
> Cc: Wang, Jian J <jian.j.wang@intel.com>; Wu, Hao A <hao.a.wu@intel.com>;
> Gao, Zhichao <zhichao.gao@intel.com>; Ni, Ray <ray.ni@intel.com>
> Subject: [PATCH] MdeModulePkg: Fix device path when the boot manager
> menu is from different FV
> 
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3441
> 
> When the boot manager menu is from different FV, the current logic still use
> the
> device path of the FV as the module links to this library
> 
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Zhichao Gao <zhichao.gao@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Signed-off-by: Zhiguang Liu <zhiguang.liu@intel.com>
> ---
>  MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c | 28 +++-------------
> ------------
>  1 file changed, 3 insertions(+), 25 deletions(-)
> 
> diff --git a/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> b/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> index bef41ae102..95d185b639 100644
> --- a/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> +++ b/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> @@ -2405,13 +2405,9 @@ BmRegisterBootManagerMenu (
>    CHAR16                             *Description;
> 
>    UINTN                              DescriptionLength;
> 
>    EFI_DEVICE_PATH_PROTOCOL           *DevicePath;
> 
> -  EFI_LOADED_IMAGE_PROTOCOL          *LoadedImage;
> 
> -  MEDIA_FW_VOL_FILEPATH_DEVICE_PATH  FileNode;
> 
>    UINTN                              HandleCount;
> 
>    EFI_HANDLE                         *Handles;
> 
>    UINTN                              Index;
> 
> -  VOID                               *Data;
> 
> -  UINTN                              DataSize;
> 
> 
> 
>    DevicePath = NULL;
> 
>    Description = NULL;
> 
> @@ -2437,22 +2433,17 @@ BmRegisterBootManagerMenu (
>    }
> 
> 
> 
>    if (DevicePath == NULL) {
> 
> -    Data = NULL;
> 
> -    Status = GetSectionFromAnyFv (
> 
> +    Status = GetFileDevicePathFromAnyFv (
> 
>                 PcdGetPtr (PcdBootManagerMenuFile),
> 
>                 EFI_SECTION_PE32,
> 
>                 0,
> 
> -               (VOID **) &Data,
> 
> -               &DataSize
> 
> +               &DevicePath
> 
>                 );
> 
> -    if (Data != NULL) {
> 
> -      FreePool (Data);
> 
> -    }
> 
>      if (EFI_ERROR (Status)) {
> 
>        DEBUG ((EFI_D_WARN, "[Bds]BootManagerMenu FFS section can not be
> found, skip its boot option registration\n"));
> 
>        return EFI_NOT_FOUND;
> 
>      }
> 
> -
> 
> +    ASSERT (DevicePath != NULL);
> 
>      //
> 
>      // Get BootManagerMenu application's description from EFI User
> Interface Section.
> 
>      //
> 
> @@ -2466,19 +2457,6 @@ BmRegisterBootManagerMenu (
>      if (EFI_ERROR (Status)) {
> 
>        Description = NULL;
> 
>      }
> 
> -
> 
> -    EfiInitializeFwVolDevicepathNode (&FileNode, PcdGetPtr
> (PcdBootManagerMenuFile));
> 
> -    Status = gBS->HandleProtocol (
> 
> -                    gImageHandle,
> 
> -                    &gEfiLoadedImageProtocolGuid,
> 
> -                    (VOID **) &LoadedImage
> 
> -                    );
> 
> -    ASSERT_EFI_ERROR (Status);
> 
> -    DevicePath = AppendDevicePathNode (
> 
> -                   DevicePathFromHandle (LoadedImage->DeviceHandle),
> 
> -                   (EFI_DEVICE_PATH_PROTOCOL *) &FileNode
> 
> -                   );
> 
> -    ASSERT (DevicePath != NULL);
> 
>    }
> 
> 
> 
>    Status = EfiBootManagerInitializeLoadOption (
> 
> --
> 2.30.0.windows.2


  reply	other threads:[~2021-06-09  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  9:37 [PATCH] MdeModulePkg: Fix device path when the boot manager menu is from different FV Zhiguang Liu
2021-06-09  9:50 ` Ni, Ray [this message]
2021-06-15  3:21 ` Wu, Hao A

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO1PR11MB49305A0B5DC7314118E02FA28C369@CO1PR11MB4930.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox