public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Fan, Jeff" <jeff.fan@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Tian, Feng" <feng.tian@intel.com>,
	"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH] MdeModulePkg/UefiBootManagerLib: Avoid buggy USB short-form expanding
Date: Thu, 20 Apr 2017 06:15:16 +0000	[thread overview]
Message-ID: <542CF652F8836A4AB8DBFAAD40ED192A4C5A9A8D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5B9361D4@SHSMSX104.ccr.corp.intel.com>

Reviewed-by: Jeff Fan <jeff.fan@intel.com>

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of 
> Ruiyu Ni
> Sent: Wednesday, April 19, 2017 5:17 PM
> To: edk2-devel@lists.01.org
> Cc: Tian, Feng <feng.tian@intel.com>; Michael Turner 
> <Michael.Turner@microsoft.com>; Fan, Jeff <jeff.fan@intel.com>; Dong, 
> Eric <eric.dong@intel.com>
> Subject: [edk2] [PATCH] MdeModulePkg/UefiBootManagerLib: Avoid buggy 
> USB short-form expanding
> 
> When a load option points to a physical UsbIo controller, whose device 
> path contains UsbClass or UsbWwid node, old logic unconditionally 
> treats it as a short-form device path and expands it. But the 
> expanding gets the exactly same device path, and the device path is 
> passed to
> BmGetNextLoadOptionDevicePath() which then passes this device path to
> BmExpandUsbDevicePath() again.
> This causes a infinite recursion.
> 
> The patch avoids the USB short-form expanding when the device path 
> points to a physical UsbIo controller.
> 
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Feng Tian <feng.tian@intel.com>
> Cc: Jeff Fan <jeff.fan@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Michael Turner <Michael.Turner@microsoft.com>
> ---
>  MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c | 43
> ++++++++++++++----------
>  1 file changed, 26 insertions(+), 17 deletions(-)
> 
> diff --git a/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> b/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> index aa79c90..d684482 100644
> --- a/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> +++ b/MdeModulePkg/Library/UefiBootManagerLib/BmBoot.c
> @@ -1546,26 +1546,35 @@ BmGetNextLoadOptionDevicePath (
>      //
>      return BmExpandUriDevicePath (FilePath, FullPath);
>    } else {
> -    for (Node = FilePath; !IsDevicePathEnd (Node); Node =
> NextDevicePathNode (Node)) {
> -      if ((DevicePathType (Node) == MESSAGING_DEVICE_PATH) &&
> -          ((DevicePathSubType (Node) == MSG_USB_CLASS_DP) ||
> (DevicePathSubType (Node) == MSG_USB_WWID_DP))) {
> -        break;
> +    Node = FilePath;
> +    Status = gBS->LocateDevicePath (&gEfiUsbIoProtocolGuid, &Node,
> &Handle);
> +    if (EFI_ERROR (Status)) {
> +      //
> +      // Only expand the USB WWID/Class device path
> +      // when FilePath doesn't point to a physical UsbIo controller.
> +      // Otherwise, infinite recursion will happen.
> +      //
> +      for (Node = FilePath; !IsDevicePathEnd (Node); Node =
> NextDevicePathNode (Node)) {
> +        if ((DevicePathType (Node) == MESSAGING_DEVICE_PATH) &&
> +            ((DevicePathSubType (Node) == MSG_USB_CLASS_DP) ||
> (DevicePathSubType (Node) == MSG_USB_WWID_DP))) {
> +          break;
> +        }
>        }
> -    }
> 
> -    //
> -    // Expand the USB WWID/Class device path
> -    //
> -    if (!IsDevicePathEnd (Node)) {
> -      if (FilePath == Node) {
> -        //
> -        // Boot Option device path starts with USB Class or USB WWID device
> path.
> -        // For Boot Option device path which doesn't begin with the USB Class
> or
> -        // USB WWID device path, it's not needed to connect again here.
> -        //
> -        BmConnectUsbShortFormDevicePath (FilePath);
> +      //
> +      // Expand the USB WWID/Class device path
> +      //
> +      if (!IsDevicePathEnd (Node)) {
> +        if (FilePath == Node) {
> +          //
> +          // Boot Option device path starts with USB Class or USB 
> + WWID device
> path.
> +          // For Boot Option device path which doesn't begin with the 
> + USB Class
> or
> +          // USB WWID device path, it's not needed to connect again here.
> +          //
> +          BmConnectUsbShortFormDevicePath (FilePath);
> +        }
> +        return BmExpandUsbDevicePath (FilePath, FullPath, Node);
>        }
> -      return BmExpandUsbDevicePath (FilePath, FullPath, Node);
>      }
>    }
> 
> --
> 2.9.0.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2017-04-20  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  9:17 [PATCH] MdeModulePkg/UefiBootManagerLib: Avoid buggy USB short-form expanding Ruiyu Ni
     [not found] ` <734D49CCEBEEF84792F5B80ED585239D5B9361D4@SHSMSX104.ccr.corp.intel.com>
2017-04-20  6:15   ` Fan, Jeff [this message]

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=542CF652F8836A4AB8DBFAAD40ED192A4C5A9A8D@shsmsx102.ccr.corp.intel.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