From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif@nuviainc.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH 1/1] ArmPkg/MmCommunicationDxe: fix logic bug in DXE driver entrypoint
Date: Mon, 2 Mar 2020 14:00:54 +0100 [thread overview]
Message-ID: <CAKv+Gu_Y7cUzOBVJPk0Z0ekM3aLT0YgtrMOEF4HerV9epnu1aQ@mail.gmail.com> (raw)
In-Reply-To: <20200302125744.GG23627@bivouac.eciton.net>
On Mon, 2 Mar 2020 at 13:57, Leif Lindholm <leif@nuviainc.com> wrote:
>
> On Wed, Feb 26, 2020 at 13:41:03 +0100, Ard Biesheuvel wrote:
> > Commit 2fe25a74d6fee3c2 ("ArmPkg/MmCommunicationDxe: relay architected PI
> > events to MM context") update the ARM specific standalone MM client
> > driver to register for certain events in the entrypoint code, but did
> > so in a way that makes the entrypoint always return with an error.
> >
> > Instead, return EFI_SUCCESS if registering for those events succeeds,
> > and back out the registrations that did succeed if one fails, and
> > return an error.
> >
> > Fixes: 2fe25a74d6fee3c2 ("ArmPkg/MmCommunicationDxe: relay architected PI events to MM context")
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Reviewed-by: Leif Lindholm <leif@nuviainc.com>
>
Thanks.
> Are you looking for this one to make the stable tag? You're not
> explicitly asking for it, but you're cc:ing Liming.
>
I don't think it is terribly useful to get this into the stable tag,
given that the standalone MM support is not complete yet, and stalled
on a PI spec update.
But by the same reasoning, it could go in as well, since it is an
obvious bugfix, and the risk is low.
I don't really care either way tbh, I just wanted to make Liming aware of it.
> > ---
> > ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> > index a4ee4dcd864c..6c06b3574861 100644
> > --- a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> > +++ b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> > @@ -385,8 +385,16 @@ MmCommunication2Initialize (
> > MmGuidedEventNotify, mGuidedEventGuid[Index],
> > mGuidedEventGuid[Index], &mGuidedEvent[Index]);
> > ASSERT_EFI_ERROR (Status);
> > + if (EFI_ERROR (Status)) {
> > + while (Index-- > 0) {
> > + gBS->CloseEvent (mGuidedEvent[Index]);
> > + }
> > + goto UninstallProtocol;
> > + }
> > }
> > + return EFI_SUCCESS;
> >
> > +UninstallProtocol:
> > gBS->UninstallProtocolInterface (
> > mMmCommunicateHandle,
> > &gEfiMmCommunication2ProtocolGuid,
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2020-03-02 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 12:41 [PATCH 1/1] ArmPkg/MmCommunicationDxe: fix logic bug in DXE driver entrypoint Ard Biesheuvel
2020-03-02 12:57 ` Leif Lindholm
2020-03-02 13:00 ` Ard Biesheuvel [this message]
2020-03-02 13:12 ` Leif Lindholm
2020-03-04 17:44 ` Ard Biesheuvel
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=CAKv+Gu_Y7cUzOBVJPk0Z0ekM3aLT0YgtrMOEF4HerV9epnu1aQ@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