From: "Wu, Hao A" <hao.a.wu@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [PATCH v2] MdeModulePkg/DxeCore: Please static checker for false report
Date: Fri, 26 Apr 2019 05:38:55 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8C41E0@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu8EJ=fCpO6cauHHh9PdVVnBWMLBK7BfdfCNL7G6w6KB-Q@mail.gmail.com>
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Wednesday, April 24, 2019 3:07 PM
> To: Wu, Hao A
> Cc: edk2-devel-groups-io; Kinney, Michael D; Gao, Liming; Wang, Jian J
> Subject: Re: [PATCH v2] MdeModulePkg/DxeCore: Please static checker for
> false report
>
> On Wed, 24 Apr 2019 at 07:05, Hao Wu <hao.a.wu@intel.com> wrote:
> >
> > After commit 57df17fe26, some static check reports suspicous NULL pointer
> > deference at line:
> >
> > Entry->MachineType = Entry->Emulator->MachineType;
> > ^^^^^^^^^^^^^^^
> >
> > within function PeCoffEmuProtocolNotify().
> >
> > However, 'Entry->Emulator' is guaranteed to have a non-NULL value when
> > previous call to the CoreHandleProtocol() returns EFI_SUCCESS.
> >
> > This commit will re-write the return status check for CoreHandleProtocol()
> > to add explicit NULL pointer check for protocol instance pointer.
> >
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Cc: Michael D Kinney <michael.d.kinney@intel.com>
> > Cc: Liming Gao <liming.gao@intel.com>
> > Cc: Jian J Wang <jian.j.wang@intel.com>
> > Signed-off-by: Hao Wu <hao.a.wu@intel.com>
>
> Again, I think it is rather unfortunate that we need code changes such
> as this one just to remove warnings from a flawed static analyzer. But
> the change looks correct to me, so
>
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Thanks Ard,
Hello Mike, Liming and Jian,
Do you have additional feedbacks on this patch?
If not, I plan to push it with the 'Ack' tag from Ard.
Best Regards,
Hao Wu
>
> > ---
> > MdeModulePkg/Core/Dxe/Image/Image.c | 23 ++++++++++++--------
> > 1 file changed, 14 insertions(+), 9 deletions(-)
> >
> > diff --git a/MdeModulePkg/Core/Dxe/Image/Image.c
> b/MdeModulePkg/Core/Dxe/Image/Image.c
> > index 08306a73fd..de5b8bed27 100644
> > --- a/MdeModulePkg/Core/Dxe/Image/Image.c
> > +++ b/MdeModulePkg/Core/Dxe/Image/Image.c
> > @@ -134,12 +134,14 @@ PeCoffEmuProtocolNotify (
> > IN VOID *Context
> > )
> > {
> > - EFI_STATUS Status;
> > - UINTN BufferSize;
> > - EFI_HANDLE EmuHandle;
> > - EMULATOR_ENTRY *Entry;
> > + EFI_STATUS Status;
> > + UINTN BufferSize;
> > + EFI_HANDLE EmuHandle;
> > + EDKII_PECOFF_IMAGE_EMULATOR_PROTOCOL *Emulator;
> > + EMULATOR_ENTRY *Entry;
> >
> > EmuHandle = NULL;
> > + Emulator = NULL;
> >
> > while (TRUE) {
> > BufferSize = sizeof (EmuHandle);
> > @@ -157,16 +159,19 @@ PeCoffEmuProtocolNotify (
> > return;
> > }
> >
> > - Entry = AllocateZeroPool (sizeof (*Entry));
> > - ASSERT (Entry != NULL);
> > -
> > Status = CoreHandleProtocol (
> > EmuHandle,
> > &gEdkiiPeCoffImageEmulatorProtocolGuid,
> > - (VOID **)&Entry->Emulator
> > + (VOID **)&Emulator
> > );
> > - ASSERT_EFI_ERROR (Status);
> > + if (EFI_ERROR (Status) || Emulator == NULL) {
> > + continue;
> > + }
> > +
> > + Entry = AllocateZeroPool (sizeof (*Entry));
> > + ASSERT (Entry != NULL);
> >
> > + Entry->Emulator = Emulator;
> > Entry->MachineType = Entry->Emulator->MachineType;
> >
> > InsertTailList (&mAvailableEmulators, &Entry->Link);
> > --
> > 2.12.0.windows.1
> >
next prev parent reply other threads:[~2019-04-26 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 5:05 [PATCH v2] MdeModulePkg/DxeCore: Please static checker for false report Wu, Hao A
2019-04-24 7:07 ` Ard Biesheuvel
2019-04-26 5:38 ` Wu, Hao A [this message]
2019-04-26 7:32 ` Liming Gao
2019-04-26 14:50 ` Michael D Kinney
2019-04-28 0:33 ` Wu, Hao A
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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8C41E0@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