From: "Nickle Wang via groups.io" <nicklew=nvidia.com@groups.io>
To: Mike Maslenkin <mike.maslenkin@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"abner.chang@amd.com" <abner.chang@amd.com>
Cc: "igork@ami.com" <igork@ami.com>
Subject: Re: [edk2-devel] [PATCH v2 1/6] RedfishClientPkg: fix crash on access to uninialized list variable.
Date: Wed, 30 Aug 2023 01:47:40 +0000 [thread overview]
Message-ID: <MW4PR12MB70315CB1F46BDA1A27393C6BD9E6A@MW4PR12MB7031.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230829080112.12748-2-mike.maslenkin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
Reviewed-by: Nickle Wang <nicklew@nvidia.com>
@abner.chang@amd.com<mailto:abner.chang@amd.com>, I am thinking that we may need to provide allocation function for CS structure so caller does not need to handle linked-list initialization like this one, or other stuff requies understanding to CS structure implementation.
Regards,
Nickle
> -----Original Message-----
> From: Mike Maslenkin <mike.maslenkin@gmail.com>
> Sent: Tuesday, August 29, 2023 4:01 PM
> To: devel@edk2.groups.io
> Cc: abner.chang@amd.com; Nickle Wang <nicklew@nvidia.com>;
> igork@ami.com; Mike Maslenkin <mike.maslenkin@gmail.com>
> Subject: [PATCH v2 1/6] RedfishClientPkg: fix crash on access to uninialized list
> variable.
>
> External email: Use caution opening links or attachments
>
>
> Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com<mailto:mike.maslenkin@gmail.com>>
> ---
> RedfishClientPkg/Features/Bios/v1_0_9/Common/BiosCommon.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/RedfishClientPkg/Features/Bios/v1_0_9/Common/BiosCommon.c
> b/RedfishClientPkg/Features/Bios/v1_0_9/Common/BiosCommon.c
> index b9c799e07684..a1738de46fdf 100644
> --- a/RedfishClientPkg/Features/Bios/v1_0_9/Common/BiosCommon.c
> +++ b/RedfishClientPkg/Features/Bios/v1_0_9/Common/BiosCommon.c
> @@ -97,6 +97,8 @@ RedfishConsumeResourceCommon (
> if (BiosCs->Attributes == NULL) {
>
> BiosCs->Attributes = AllocateZeroPool (sizeof
> (RedfishBios_V1_0_9_Attributes_CS));
>
> ASSERT (BiosCs->Attributes != NULL);
>
> + // initialize list
>
> + BiosCs->Attributes->Prop.ForwardLink = &BiosCs->Attributes->Prop;
>
> }
>
>
>
> //
>
> --
> 2.32.0 (Apple Git-132)
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108105): https://edk2.groups.io/g/devel/message/108105
Mute This Topic: https://groups.io/mt/101027003/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 6254 bytes --]
next prev parent reply other threads:[~2023-08-30 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 8:01 [edk2-devel] [PATCH v2 0/6] RedfishClientPkg: fix issues with local variables Mike Maslenkin
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 1/6] RedfishClientPkg: fix crash on access to uninialized list variable Mike Maslenkin
2023-08-30 1:47 ` Nickle Wang via groups.io [this message]
2023-08-31 3:28 ` Chang, Abner via groups.io
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 2/6] RedfishClientPkg: fix access to uninitialized variable Mike Maslenkin
2023-08-30 1:48 ` Nickle Wang via groups.io
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 3/6] RedfishClientPkg: fix leak of allocated Etag data Mike Maslenkin
2023-08-30 1:49 ` Nickle Wang via groups.io
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 4/6] RedfishClientPkg: fix memory leak during EFI variables write Mike Maslenkin
2023-08-30 1:49 ` Nickle Wang via groups.io
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 5/6] RedfishClientPkg: fix misprints in Readme.md Mike Maslenkin
2023-08-30 1:51 ` Nickle Wang via groups.io
2023-08-29 8:01 ` [edk2-devel] [PATCH v2 6/6] RedfishClientPkg: spelling fixes Mike Maslenkin
2023-08-30 1:52 ` Nickle Wang via groups.io
2023-08-30 15:30 ` Igor Kulchytskyy via groups.io
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=MW4PR12MB70315CB1F46BDA1A27393C6BD9E6A@MW4PR12MB7031.namprd12.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