From: "Zhiguang Liu" <zhiguang.liu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Liming Gao <gaoliming@byosoft.com.cn>,
"Wu, Jiaxin" <jiaxin.wu@intel.com>, "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 2/4] MdeModulePkg/SMM: Disallow unregister SMI handler in other SMI handler
Date: Wed, 28 Feb 2024 08:52:39 +0000 [thread overview]
Message-ID: <PH0PR11MB504809B7D8572ABAD0E38A2790582@PH0PR11MB5048.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7e5bff6c-04b0-4c91-3fa1-514e10e14481@redhat.com>
Thanks Laszlo. Both are good comments. I will follow in next version
Thanks
Zhiguang
> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Wednesday, February 28, 2024 4:45 PM
> To: devel@edk2.groups.io; Liu, Zhiguang <zhiguang.liu@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>; Wu, Jiaxin
> <jiaxin.wu@intel.com>; Ni, Ray <ray.ni@intel.com>
> Subject: Re: [edk2-devel] [PATCH v2 2/4] MdeModulePkg/SMM: Disallow
> unregister SMI handler in other SMI handler
>
> On 2/28/24 03:27, Zhiguang Liu wrote:
> > In last patch, we add code support to unregister SMI handler inside
> > itself. However, the code doesn't support unregister SMI handler
> > insider other SMI handler. While this is not a must-have usage.
> > So add check to disallow unregister SMI handler in other SMI handler.
> >
> > Cc: Liming Gao <gaoliming@byosoft.com.cn>
> > Cc: Jiaxin Wu <jiaxin.wu@intel.com>
> > Cc: Ray Ni <ray.ni@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Signed-off-by: Zhiguang Liu <zhiguang.liu@intel.com>
> > ---
> > MdeModulePkg/Core/PiSmmCore/Smi.c | 32
> > +++++++++++++++++++++++--------
> > 1 file changed, 24 insertions(+), 8 deletions(-)
> >
> > diff --git a/MdeModulePkg/Core/PiSmmCore/Smi.c
> > b/MdeModulePkg/Core/PiSmmCore/Smi.c
> > index 3489c130fd..1bfbc635fc 100644
> > --- a/MdeModulePkg/Core/PiSmmCore/Smi.c
> > +++ b/MdeModulePkg/Core/PiSmmCore/Smi.c
> > @@ -8,7 +8,8 @@
> >
> > #include "PiSmmCore.h"
> >
> > -LIST_ENTRY mSmiEntryList = INITIALIZE_LIST_HEAD_VARIABLE
> > (mSmiEntryList);
> > +SMI_HANDLER *gCurrentSmiHandler = NULL;
> > +LIST_ENTRY mSmiEntryList = INITIALIZE_LIST_HEAD_VARIABLE
> (mSmiEntryList);
> >
> > SMI_ENTRY mRootSmiEntry = {
> > SMI_ENTRY_SIGNATURE,
> > @@ -142,13 +143,18 @@ SmiManage (
> > // Link points to may be freed if unregister SMI handler.
> > //
> > Link = Link->ForwardLink;
> > -
> > - Status = SmiHandler->Handler (
> > - (EFI_HANDLE)SmiHandler,
> > - Context,
> > - CommBuffer,
> > - CommBufferSize
> > - );
> > + //
> > + // Assign gCurrentSmiHandle before calling the SMI handler and
> > + // set to NULL when it returns.
> > + //
> > + gCurrentSmiHandler = SmiHandler;
> > + Status = SmiHandler->Handler (
> > + (EFI_HANDLE)SmiHandler,
> > + Context,
> > + CommBuffer,
> > + CommBufferSize
> > + );
> > + gCurrentSmiHandler = NULL;
> >
> > switch (Status) {
> > case EFI_INTERRUPT_PENDING:
> > @@ -328,6 +334,16 @@ SmiHandlerUnRegister (
> > return EFI_INVALID_PARAMETER;
> > }
> >
> > + //
> > + // Check if unregister SMI handler inside a SMI Handler // if
> > + (gCurrentSmiHandler != NULL) {
> > + //
> > + // Only allow to unregister SMI Handler inside itself.
> > + //
> > + ASSERT (gCurrentSmiHandler == SmiHandler); }
> > +
> > SmiEntry = SmiHandler->SmiEntry;
> >
> > RemoveEntryList (&SmiHandler->Link);
>
> (1) Why not:
>
> if ((gCurrentSmiHandler != NULL) && (gCurrentSmiHandler != SmiHandler)) {
> return EFI_INVALID_PARAMETER;
> }
>
> ?
>
> (2) Why do we call the new global variable "gCurrentSmiHandler" rather than
> "mCurrentSmiHandler"?
>
> Thanks
> Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116108): https://edk2.groups.io/g/devel/message/116108
Mute This Topic: https://groups.io/mt/104616993/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-28 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 2:27 [edk2-devel] [PATCH v2 0/4] Support to unregister SMI handler inside SMI handler Zhiguang Liu
2024-02-28 2:27 ` [edk2-devel] [PATCH v2 1/4] MdeModulePkg/SMM: " Zhiguang Liu
2024-02-29 12:24 ` Ni, Ray
2024-02-28 2:27 ` [edk2-devel] [PATCH v2 2/4] MdeModulePkg/SMM: Disallow unregister SMI handler in other " Zhiguang Liu
2024-02-28 8:45 ` Laszlo Ersek
2024-02-28 8:52 ` Zhiguang Liu [this message]
2024-02-28 2:27 ` [edk2-devel] [PATCH v2 3/4] StandaloneMmPkg: Support to unregister MMI handler inside MMI handler Zhiguang Liu
2024-02-28 8:47 ` Laszlo Ersek
2024-02-29 12:24 ` Ni, Ray
2024-03-11 14:02 ` Ard Biesheuvel
2024-02-28 2:27 ` [edk2-devel] [PATCH v2 4/4] StandaloneMmPkg: Disallow unregister MMI handler in other " Zhiguang Liu
2024-02-28 8:47 ` Laszlo Ersek
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=PH0PR11MB504809B7D8572ABAD0E38A2790582@PH0PR11MB5048.namprd11.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