From: "Laszlo Ersek" <lersek@redhat.com>
To: Wenyi Xie <xiewenyi2@huawei.com>,
devel@edk2.groups.io, jiewen.yao@intel.com,
jian.j.wang@intel.com
Cc: songdongkuang@huawei.com
Subject: Re: [PATCH EDK2 v1 1/1] SecurityPkg/FvReportPei: remove redundant sizeof
Date: Tue, 13 Apr 2021 15:16:39 +0200 [thread overview]
Message-ID: <c274b9e6-3808-52ca-5452-59735a49bb42@redhat.com> (raw)
In-Reply-To: <1618317217-112644-2-git-send-email-xiewenyi2@huawei.com>
On 04/13/21 14:33, Wenyi Xie wrote:
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3333
>
> In function InstallPreHashFvPpi, when calculatuing the size
(1) s/calculatuing/calculating/
(2) I suggest remarking, in the commit message, that this bug does not
lead to buffer overflow, given that "sizeof (HASH_INFO)" is 4, whereas
"sizeof (sizeof (HASH_INFO))" is 4 or 8.
> of struct HASH_INFO,sizeof is used twice.
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Wenyi Xie <xiewenyi2@huawei.com>
> ---
> SecurityPkg/FvReportPei/FvReportPei.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/SecurityPkg/FvReportPei/FvReportPei.c b/SecurityPkg/FvReportPei/FvReportPei.c
> index d709760ea3ce..e82413e090c0 100644
> --- a/SecurityPkg/FvReportPei/FvReportPei.c
> +++ b/SecurityPkg/FvReportPei/FvReportPei.c
> @@ -67,7 +67,7 @@ InstallPreHashFvPpi (
> HASH_INFO *HashInfo;
>
> PpiSize = sizeof (EDKII_PEI_FIRMWARE_VOLUME_INFO_PREHASHED_FV_PPI)
> - + sizeof (sizeof (HASH_INFO))
> + + sizeof (HASH_INFO)
> + HashSize;
>
> PreHashedFvPpi = AllocatePool (PpiSize);
>
>From my perspective:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
prev parent reply other threads:[~2021-04-13 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 12:33 [PATCH EDK2 v1 0/1] SecurityPkg/FvReportPei: remove redundant sizeof wenyi,xie
2021-04-13 12:33 ` [PATCH EDK2 v1 1/1] " wenyi,xie
2021-04-13 13:16 ` Laszlo Ersek [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=c274b9e6-3808-52ca-5452-59735a49bb42@redhat.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