From: "Yang Jie" <jie.yang@intel.com>
To: "Xu, Wei6" <wei6.xu@intel.com>,
gaoliming <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel][PATCH] FmpDevicePkg/FmpDxe: Use new Variable Lock interface
Date: Tue, 19 Oct 2021 02:38:06 +0000 [thread overview]
Message-ID: <SN6PR11MB25905135A17C1D919A41F7FE96BD9@SN6PR11MB2590.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN7PR11MB2770A1D1F4E468DC72E88330A1BD9@BN7PR11MB2770.namprd11.prod.outlook.com>
Thank you very much for your review, but I find I missed something in the definition of the function LockFmpVariable, it is defined as follow:
static
EFI_STATUS
LockFmpVariable (
IN EFI_STATUS PreviousStatus,
EDKII_VARIABLE_POLICY_PROTOCOL *VariablePolicy,
IN CHAR16 *VariableName
)
I need to add IN ahead EDKII_VARIABLE_POLICY_PROTOCOL *VariablePolicy. I am sorry for the mistake, and I will submit a patch to fix it.
-----Original Message-----
From: Xu, Wei6 <wei6.xu@intel.com>
Sent: Tuesday, October 19, 2021 10:06 AM
To: devel@edk2.groups.io; gaoliming@byosoft.com.cn; Yang, Jie <jie.yang@intel.com>
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Jiang, Guomin <guomin.jiang@intel.com>
Subject: RE: [edk2-devel][PATCH] FmpDevicePkg/FmpDxe: Use new Variable Lock interface
Reviewed-by: Wei6 Xu <wei6.xu@intel.com>
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of gaoliming
Sent: Tuesday, October 19, 2021 9:47 AM
To: devel@edk2.groups.io; Yang, Jie <jie.yang@intel.com>
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Jiang, Guomin <guomin.jiang@intel.com>; Xu, Wei6 <wei6.xu@intel.com>
Subject: 回复: [edk2-devel][PATCH] FmpDevicePkg/FmpDxe: Use new Variable Lock interface
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Yang Jie
> 发送时间: 2021年10月18日 13:14
> 收件人: devel@edk2.groups.io
> 抄送: gaoliming@byosoft.com.cn; michael.d.kinney@intel.com;
> guomin.jiang@intel.com; wei6.xu@intel.com; yangjie
> <jie.yang@intel.com>
> 主题: [edk2-devel][PATCH] FmpDevicePkg/FmpDxe: Use new Variable Lock
> interface
>
> From: yangjie <jie.yang@intel.com>
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3655
>
> The code in FmpDevicePkg called the deprecated interface
>
> VariableLockRequestToLock. So I changed the code in
>
> FmpDevicePkg using RegisterBasicVariablePolicy,
>
> instead of the deprecated interface.
>
> Signed-off-by: Yang Jie <jie.yang@intel.com>
>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>
> Cc: Guomin Jiang <guomin.jiang@intel.com>
>
> Cc: Wei6 Xu <wei6.xu@intel.com>
> ---
> FmpDevicePkg/FmpDevicePkg.dsc | 1 +
> FmpDevicePkg/FmpDxe/FmpDxe.h | 4 +-
> FmpDevicePkg/FmpDxe/FmpDxe.inf | 5 ++-
> FmpDevicePkg/FmpDxe/VariableSupport.c | 65
> +++++++++++++--------------
> 4 files changed, 37 insertions(+), 38 deletions(-)
>
> diff --git a/FmpDevicePkg/FmpDevicePkg.dsc
> b/FmpDevicePkg/FmpDevicePkg.dsc index b420f52a08..7b1af285dd 100644
> --- a/FmpDevicePkg/FmpDevicePkg.dsc
> +++ b/FmpDevicePkg/FmpDevicePkg.dsc
> @@ -53,6 +53,7 @@
> DebugLib|MdePkg/Library/UefiDebugLibStdErr/UefiDebugLibStdErr.inf
>
>
> DebugPrintErrorLevelLib|MdePkg/Library/BaseDebugPrintErrorLevelLib/Bas
> DebugPrintErrorLevelLib|e
> DebugPrintErrorLevelLib.inf
>
> PcdLib|MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf
>
> +
> VariablePolicyHelperLib|MdeModulePkg/Library/VariablePolicyHelperLib/V
> VariablePolicyHelperLib|ari
> ablePolicyHelperLib.inf
>
> !ifdef CONTINUOUS_INTEGRATION
>
>
> BaseCryptLib|CryptoPkg/Library/BaseCryptLibNull/BaseCryptLibNull.inf
>
> !else
>
> diff --git a/FmpDevicePkg/FmpDxe/FmpDxe.h
> b/FmpDevicePkg/FmpDxe/FmpDxe.h index 1177b1828e..4d94a925b6 100644
> --- a/FmpDevicePkg/FmpDxe/FmpDxe.h
> +++ b/FmpDevicePkg/FmpDxe/FmpDxe.h
> @@ -4,7 +4,7 @@
> information provided through PCDs and libraries.
>
>
>
> Copyright (c) Microsoft Corporation.<BR>
>
> - Copyright (c) 2018 - 2019, Intel Corporation. All rights
> reserved.<BR>
>
> + Copyright (c) 2018 - 2021, Intel Corporation. All rights
> + reserved.<BR>
>
>
>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
>
>
> @@ -33,11 +33,11 @@
> #include <Library/FmpDependencyDeviceLib.h>
>
> #include <Protocol/FirmwareManagement.h>
>
> #include <Protocol/FirmwareManagementProgress.h>
>
> -#include <Protocol/VariableLock.h>
>
> #include <Guid/SystemResourceTable.h>
>
> #include <Guid/EventGroup.h>
>
> #include <LastAttemptStatus.h>
>
> #include <FmpLastAttemptStatus.h>
>
> +#include <Library/VariablePolicyHelperLib.h>
>
>
>
> #define VERSION_STRING_NOT_SUPPORTED L"VERSION STRING NOT SUPPORTED"
>
> #define VERSION_STRING_NOT_AVAILABLE L"VERSION STRING NOT AVAILABLE"
>
> diff --git a/FmpDevicePkg/FmpDxe/FmpDxe.inf
> b/FmpDevicePkg/FmpDxe/FmpDxe.inf index eeb904a091..1c296388b0 100644
> --- a/FmpDevicePkg/FmpDxe/FmpDxe.inf
> +++ b/FmpDevicePkg/FmpDxe/FmpDxe.inf
> @@ -4,7 +4,7 @@
> # information provided through PCDs and libraries.
>
> #
>
> # Copyright (c) 2016, Microsoft Corporation. All rights
> reserved.<BR>
>
> -# Copyright (c) 2018 - 2020, Intel Corporation. All rights
> reserved.<BR>
>
> +# Copyright (c) 2018 - 2021, Intel Corporation. All rights
> +reserved.<BR>
>
> #
>
> # SPDX-License-Identifier: BSD-2-Clause-Patent
>
> ##
>
> @@ -55,14 +55,15 @@
> FmpDependencyLib
>
> FmpDependencyCheckLib
>
> FmpDependencyDeviceLib
>
> + VariablePolicyHelperLib
>
>
>
> [Guids]
>
> gEfiEndOfDxeEventGroupGuid
>
>
>
> [Protocols]
>
> - gEdkiiVariableLockProtocolGuid ## CONSUMES
>
> gEfiFirmwareManagementProtocolGuid ## PRODUCES
>
> gEdkiiFirmwareManagementProgressProtocolGuid ## PRODUCES
>
> + gEdkiiVariablePolicyProtocolGuid ## CONSUMES
>
>
>
> [Pcd]
>
> gFmpDevicePkgTokenSpaceGuid.PcdFmpDeviceStorageAccessEnable
> ## CONSUMES
>
> diff --git a/FmpDevicePkg/FmpDxe/VariableSupport.c
> b/FmpDevicePkg/FmpDxe/VariableSupport.c
> index 86dd5b203b..a1bd949b09 100644
> --- a/FmpDevicePkg/FmpDxe/VariableSupport.c
> +++ b/FmpDevicePkg/FmpDxe/VariableSupport.c
> @@ -3,7 +3,7 @@
> firmware updates.
>
>
>
> Copyright (c) 2016, Microsoft Corporation. All rights reserved.<BR>
>
> - Copyright (c) 2018 - 2019, Intel Corporation. All rights
> reserved.<BR>
>
> + Copyright (c) 2018 - 2021, Intel Corporation. All rights
> + reserved.<BR>
>
>
>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
>
>
> @@ -730,28 +730,29 @@ static
> EFI_STATUS
>
> LockFmpVariable (
>
> IN EFI_STATUS PreviousStatus,
>
> - IN EDKII_VARIABLE_LOCK_PROTOCOL *VariableLock,
>
> + EDKII_VARIABLE_POLICY_PROTOCOL *VariablePolicy,
>
> IN CHAR16 *VariableName
>
> )
>
> {
>
> EFI_STATUS Status;
>
>
>
> - Status = VariableLock->RequestToLock (
>
> - VariableLock,
>
> - VariableName,
>
> - &gEfiCallerIdGuid
>
> - );
>
> - if (!EFI_ERROR (Status)) {
>
> - return PreviousStatus;
>
> + // If success, go ahead and set the policies to protect the target
variables.
>
> + Status = RegisterBasicVariablePolicy (VariablePolicy,
>
> + &gEfiCallerIdGuid,
>
> + VariableName,
>
> +
> VARIABLE_POLICY_NO_MIN_SIZE,
>
> +
> VARIABLE_POLICY_NO_MAX_SIZE,
>
> +
> VARIABLE_POLICY_NO_MUST_ATTR,
>
> +
> VARIABLE_POLICY_NO_CANT_ATTR,
>
> +
> VARIABLE_POLICY_TYPE_LOCK_NOW);
>
> + if (EFI_ERROR (Status)) {
>
> + DEBUG ((DEBUG_ERROR, "FmpDxe(%s): Failed to lock variable %g %s.
> Status = %r\n",
>
> + mImageIdName,
>
> + &gEfiCallerIdGuid,
>
> + VariableName,
>
> + Status
>
> + ));
>
> }
>
> -
>
> - DEBUG ((DEBUG_ERROR, "FmpDxe(%s): Failed to lock variable %g %s.
> Status = %r\n",
>
> - mImageIdName,
>
> - &gEfiCallerIdGuid,
>
> - VariableName,
>
> - Status
>
> - ));
>
> -
>
> if (EFI_ERROR (PreviousStatus)) {
>
> return PreviousStatus;
>
> }
>
> @@ -773,26 +774,22 @@ LockAllFmpVariables (
> FIRMWARE_MANAGEMENT_PRIVATE_DATA *Private
>
> )
>
> {
>
> - EFI_STATUS Status;
>
> - EDKII_VARIABLE_LOCK_PROTOCOL *VariableLock;
>
> -
>
> - VariableLock = NULL;
>
> - Status = gBS->LocateProtocol (
>
> - &gEdkiiVariableLockProtocolGuid,
>
> - NULL,
>
> - (VOID **)&VariableLock
>
> - );
>
> - if (EFI_ERROR (Status) || VariableLock == NULL) {
>
> - DEBUG ((DEBUG_ERROR, "FmpDxe(%s): Failed to locate Variable Lock
> Protocol (%r).\n", mImageIdName, Status));
>
> - return EFI_UNSUPPORTED;
>
> + EFI_STATUS Status;
>
> + EDKII_VARIABLE_POLICY_PROTOCOL *VariablePolicy;
>
> +
>
> + // Locate the VariablePolicy protocol.
>
> + Status = gBS->LocateProtocol (&gEdkiiVariablePolicyProtocolGuid,
> + NULL,
> (VOID**)&VariablePolicy );
>
> + if (EFI_ERROR (Status)) {
>
> + DEBUG ((DEBUG_ERROR, "FmpDxe %a - Could not locate VariablePolicy
> protocol! %r\n", __FUNCTION__, Status));
>
> + return Status;
>
> }
>
>
>
> Status = EFI_SUCCESS;
>
> - Status = LockFmpVariable (Status, VariableLock,
> Private->VersionVariableName);
>
> - Status = LockFmpVariable (Status, VariableLock,
> Private->LsvVariableName);
>
> - Status = LockFmpVariable (Status, VariableLock,
> Private->LastAttemptStatusVariableName);
>
> - Status = LockFmpVariable (Status, VariableLock,
> Private->LastAttemptVersionVariableName);
>
> - Status = LockFmpVariable (Status, VariableLock,
> Private->FmpStateVariableName);
>
> + Status = LockFmpVariable (Status, VariablePolicy,
> Private->VersionVariableName);
>
> + Status = LockFmpVariable (Status, VariablePolicy,
> Private->LsvVariableName);
>
> + Status = LockFmpVariable (Status, VariablePolicy,
> Private->LastAttemptStatusVariableName);
>
> + Status = LockFmpVariable (Status, VariablePolicy,
> Private->LastAttemptVersionVariableName);
>
> + Status = LockFmpVariable (Status, VariablePolicy,
> Private->FmpStateVariableName);
>
>
>
> return Status;
>
> }
>
> --
> 2.26.2.windows.1
>
>
>
> -=-=-=-=-=-=
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#82246):
> https://edk2.groups.io/g/devel/message/82246
> Mute This Topic: https://groups.io/mt/86407503/4905953
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub
> [gaoliming@byosoft.com.cn]
> -=-=-=-=-=-=
>
next prev parent reply other threads:[~2021-10-19 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 5:14 [edk2-devel][PATCH] FmpDevicePkg/FmpDxe: Use new Variable Lock interface jie.yang
2021-10-19 1:47 ` 回复: " gaoliming
2021-10-19 2:05 ` Xu, Wei6
2021-10-19 2:38 ` Yang Jie [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-18 5:51 Xu, Wei6
2021-10-18 4:26 Yang, Jie
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=SN6PR11MB25905135A17C1D919A41F7FE96BD9@SN6PR11MB2590.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