From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] SignedCapsulePkg SystemFirmwareUpdateDxe: Fix failure caused by d69d922
Date: Mon, 16 Apr 2018 01:49:09 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503AB624DE@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1523613978-121936-1-git-send-email-star.zeng@intel.com>
Reviewed-by: jiewen.yao@intel.com
> -----Original Message-----
> From: Zeng, Star
> Sent: Friday, April 13, 2018 6:06 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>
> Subject: [PATCH] SignedCapsulePkg SystemFirmwareUpdateDxe: Fix failure
> caused by d69d922
>
> d69d9227d046211265de1fab5580c50a65944614 caused system firmware
> update
> failure. It is because FindMatchingFmpHandles() is expected to return
> handles matched, but the function returns all handles found.
>
> This patch is to fix the issue.
> This patch also assigns mSystemFmpPrivate->Handle for "case 1:" path
> in case the Handle is needed by other place in future.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
> .../SystemFirmwareUpdate/SystemFirmwareUpdateDxe.c | 21
> ++++++++++++++++-----
> 1 file changed, 16 insertions(+), 5 deletions(-)
>
> diff --git
> a/SignedCapsulePkg/Universal/SystemFirmwareUpdate/SystemFirmwareUpdate
> Dxe.c
> b/SignedCapsulePkg/Universal/SystemFirmwareUpdate/SystemFirmwareUpdat
> eDxe.c
> index d0b1c9913ca8..fa0c5f03ffdd 100644
> ---
> a/SignedCapsulePkg/Universal/SystemFirmwareUpdate/SystemFirmwareUpdate
> Dxe.c
> +++
> b/SignedCapsulePkg/Universal/SystemFirmwareUpdate/SystemFirmwareUpdat
> eDxe.c
> @@ -602,6 +602,7 @@ FindMatchingFmpHandles (
> )
> {
> EFI_STATUS Status;
> + UINTN TempHandleCount;
> EFI_HANDLE *HandleBuffer;
> UINTN Index;
> UINTN Index2;
> @@ -613,20 +614,20 @@ FindMatchingFmpHandles (
> BOOLEAN MatchFound;
>
> *HandleCount = 0;
> + TempHandleCount = 0;
> HandleBuffer = NULL;
> Status = gBS->LocateHandleBuffer (
> ByProtocol,
> ProtocolGuid,
> NULL,
> - HandleCount,
> + &TempHandleCount,
> &HandleBuffer
> );
> if (EFI_ERROR (Status)) {
> - *HandleCount = 0;
> return NULL;
> }
>
> - for (Index = 0; Index < *HandleCount; Index++) {
> + for (Index = 0; Index < TempHandleCount; Index++) {
> OriginalFmpImageInfoBuf = GetFmpImageDescriptors (
> HandleBuffer[Index],
> ProtocolGuid,
> @@ -657,12 +658,21 @@ FindMatchingFmpHandles (
> //
> FmpImageInfoBuf = (EFI_FIRMWARE_IMAGE_DESCRIPTOR *)(((UINT8
> *)FmpImageInfoBuf) + DescriptorSize);
> }
> - if (!MatchFound) {
> - HandleBuffer[Index] = NULL;
> + if (MatchFound) {
> + HandleBuffer[*HandleCount] = HandleBuffer[Index];
> + (*HandleCount)++;
> }
>
> FreePool (OriginalFmpImageInfoBuf);
> }
> +
> + if ((*HandleCount) == 0) {
> + //
> + // No any matching handle.
> + //
> + FreePool (HandleBuffer);
> + return NULL;
> + }
> return HandleBuffer;
> }
>
> @@ -801,6 +811,7 @@ SystemFirmwareUpdateMainDxe (
> // Install System FMP protocol onto handle with matching FMP Protocol
> //
> DEBUG ((DEBUG_INFO, "SystemFirmwareUpdateDxe: Install System FMP
> onto matching FMP handle\n"));
> + mSystemFmpPrivate->Handle = HandleBuffer[0];
> Status = gBS->InstallMultipleProtocolInterfaces (
> &HandleBuffer[0],
> &gSystemFmpProtocolGuid,
> --
> 2.7.0.windows.1
next prev parent reply other threads:[~2018-04-16 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 10:06 [PATCH] SignedCapsulePkg SystemFirmwareUpdateDxe: Fix failure caused by d69d922 Star Zeng
2018-04-16 1:49 ` Yao, Jiewen [this message]
2018-04-16 5:39 ` Kinney, Michael D
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=74D8A39837DF1E4DA445A8C0B3885C503AB624DE@SHSMSX104.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