From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, pierre.gondois@arm.com
Cc: Sami Mujawar <sami.mujawar@arm.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Liming Gao <gaoliming@byosoft.com.cn>,
Jiewen Yao <jiewen.yao@intel.com>,
Jian J Wang <jian.j.wang@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1][edk2-stable202211] SecurityPkg/RngDxe: Fix Rng algo selection for Arm
Date: Mon, 14 Nov 2022 20:12:24 +0100 [thread overview]
Message-ID: <CAMj1kXHxwSh32w7n7Y_CdgHxUkx89P0ZRQBPikPQ=CyszOYARQ@mail.gmail.com> (raw)
In-Reply-To: <20221114181351.1813748-1-Pierre.Gondois@arm.com>
On Mon, 14 Nov 2022 at 19:14, PierreGondois <pierre.gondois@arm.com> wrote:
>
> From: Pierre Gondois <pierre.gondois@arm.com>
>
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4151
>
> PcdCpuRngSupportedAlgorithm is set to the Zero Guid for KvmTool
> since it is not possible to predict which algorithm will be
> implemented for Arm's FEAT_RNG in the host. Current handling is:
> - skipping the Zero Guid, which should not happen to handle
> KvmTool's case,
> - triggering an ASSERT if no algorithm was found. However having
> no Rng algorithm is a valid case,
>
> Correctly handle the Zero Guid case and replace the ASSERT by a
> warning message when no Rng algorithm is found.
> Also simplify the selection of the Rng algorithm when the default
> one is selected by just picking up the first element of
> mAvailableAlgoArray.
>
Can you explain a bit more please
What is supposed to happen?
What happens instead?
Why is this patch the correct way to address this issue?
> Reported-by: Sami Mujawar <sami.mujawar@arm.com>
> Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com>
> ---
> .../RandomNumberGenerator/RngDxe/ArmRngDxe.c | 15 +++------------
> SecurityPkg/RandomNumberGenerator/RngDxe/RngDxe.c | 8 +++++++-
> 2 files changed, 10 insertions(+), 13 deletions(-)
>
> diff --git a/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c b/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
> index 5ba319899ce9..722d53386373 100644
> --- a/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
> +++ b/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
> @@ -76,7 +76,6 @@ RngGetRNG (
> )
> {
> EFI_STATUS Status;
> - UINTN Index;
>
> if ((This == NULL) || (RNGValueLength == 0) || (RNGValue == NULL)) {
> return EFI_INVALID_PARAMETER;
> @@ -86,21 +85,13 @@ RngGetRNG (
> //
> // Use the default RNG algorithm if RNGAlgorithm is NULL.
> //
> - for (Index = 0; Index < mAvailableAlgoArrayCount; Index++) {
> - if (!IsZeroGuid (&mAvailableAlgoArray[Index])) {
> - RNGAlgorithm = &mAvailableAlgoArray[Index];
> - goto FoundAlgo;
> - }
> - }
> -
> - if (Index == mAvailableAlgoArrayCount) {
> - // No algorithm available.
> - ASSERT (Index != mAvailableAlgoArrayCount);
> + if (mAvailableAlgoArrayCount != 0) {
> + RNGAlgorithm = &mAvailableAlgoArray[0];
> + } else {
> return EFI_DEVICE_ERROR;
> }
> }
>
> -FoundAlgo:
> if (CompareGuid (RNGAlgorithm, PcdGetPtr (PcdCpuRngSupportedAlgorithm))) {
> Status = RngGetBytes (RNGValueLength, RNGValue);
> return Status;
> diff --git a/SecurityPkg/RandomNumberGenerator/RngDxe/RngDxe.c b/SecurityPkg/RandomNumberGenerator/RngDxe/RngDxe.c
> index 421abb52b8bf..403b31b73609 100644
> --- a/SecurityPkg/RandomNumberGenerator/RngDxe/RngDxe.c
> +++ b/SecurityPkg/RandomNumberGenerator/RngDxe/RngDxe.c
> @@ -21,6 +21,7 @@ SPDX-License-Identifier: BSD-2-Clause-Patent
>
> #include <Library/BaseLib.h>
> #include <Library/BaseMemoryLib.h>
> +#include <Library/DebugLib.h>
> #include <Library/UefiBootServicesTableLib.h>
> #include <Library/RngLib.h>
> #include <Protocol/Rng.h>
> @@ -80,7 +81,12 @@ RngDriverEntry (
> //
> // Get the list of available algorithm.
> //
> - return GetAvailableAlgorithms ();
> + Status = GetAvailableAlgorithms ();
> + if (mAvailableAlgoArrayCount == 0) {
> + DEBUG ((DEBUG_WARN, "No Rng algorithm found in RngDxe.\n"));
> + }
> +
> + return Status;
> }
>
> /**
> --
> 2.25.1
>
>
>
> ------------
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#96356): https://edk2.groups.io/g/devel/message/96356
> Mute This Topic: https://groups.io/mt/95025606/5717338
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub [ardb+tianocore@kernel.org]
> ------------
>
>
next prev parent reply other threads:[~2022-11-14 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 18:13 [PATCH 1/1][edk2-stable202211] SecurityPkg/RngDxe: Fix Rng algo selection for Arm PierreGondois
2022-11-14 19:12 ` Ard Biesheuvel [this message]
2022-11-15 8:27 ` [edk2-devel] " PierreGondois
2022-11-16 15:04 ` PierreGondois
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='CAMj1kXHxwSh32w7n7Y_CdgHxUkx89P0ZRQBPikPQ=CyszOYARQ@mail.gmail.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