From: Ying-Tsun Huang <ying-tsun.huang@amd.com>
To: devel@edk2.groups.io
Cc: Jian J Wang <jian.j.wang@intel.com>,
Dandan Bi <dandan.bi@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: [PATCH v1 1/1] MdeModulePkg/Core: Fix the potential hang of calling SetTimer.
Date: Wed, 21 Sep 2022 10:10:23 +0800 [thread overview]
Message-ID: <20220921021023.4009-2-ying-tsun.huang@amd.com> (raw)
In-Reply-To: <20220921021023.4009-1-ying-tsun.huang@amd.com>
When calling SetTimer with Type is not TimerCancel and TriggerTime is 0,
gTimer is used to get the timer period. However, gTimer is NULL before
EFI_TIMER_ARCH_PROTOCOL is installed. Adding the check of gTimer and
return EFI_NOT_READY to avoid the hang.
Cc: Jian J Wang <jian.j.wang@intel.com>
Cc: Dandan Bi <dandan.bi@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Ying-Tsun Huang <ying-tsun.huang@amd.com>
---
MdeModulePkg/Core/Dxe/DxeMain.h | 2 ++
MdeModulePkg/Core/Dxe/Event/Timer.c | 14 ++++++++++----
2 files changed, 12 insertions(+), 4 deletions(-)
diff --git a/MdeModulePkg/Core/Dxe/DxeMain.h b/MdeModulePkg/Core/Dxe/DxeMain.h
index 815a6b4bd844..acf0b244aeda 100644
--- a/MdeModulePkg/Core/Dxe/DxeMain.h
+++ b/MdeModulePkg/Core/Dxe/DxeMain.h
@@ -1538,6 +1538,8 @@ CoreCreateEventInternal (
@retval EFI_SUCCESS The event has been set to be signaled at the
requested time
@retval EFI_INVALID_PARAMETER Event or Type is not valid
+ @retval EFI_NOT_READY Type is not TimerCancel, TriggerTime is 0, but
+ EFI_TIMER_ARCH_PROTOCOL is not installed yet
**/
EFI_STATUS
diff --git a/MdeModulePkg/Core/Dxe/Event/Timer.c b/MdeModulePkg/Core/Dxe/Event/Timer.c
index 29e507c67c50..1621814ef3c5 100644
--- a/MdeModulePkg/Core/Dxe/Event/Timer.c
+++ b/MdeModulePkg/Core/Dxe/Event/Timer.c
@@ -229,6 +229,8 @@ CoreTimerTick (
@retval EFI_SUCCESS The event has been set to be signaled at the
requested time
@retval EFI_INVALID_PARAMETER Event or Type is not valid
+ @retval EFI_NOT_READY Type is not TimerCancel, TriggerTime is 0, but
+ EFI_TIMER_ARCH_PROTOCOL is not installed yet
**/
EFI_STATUS
@@ -255,6 +257,14 @@ CoreSetTimer (
return EFI_INVALID_PARAMETER;
}
+ if ((Type != TimerCancel) && (TriggerTime == 0)) {
+ if (gTimer) {
+ gTimer->GetTimerPeriod (gTimer, &TriggerTime);
+ } else {
+ return EFI_NOT_READY;
+ }
+ }
+
CoreAcquireLock (&mEfiTimerLock);
//
@@ -270,10 +280,6 @@ CoreSetTimer (
if (Type != TimerCancel) {
if (Type == TimerPeriodic) {
- if (TriggerTime == 0) {
- gTimer->GetTimerPeriod (gTimer, &TriggerTime);
- }
-
Event->Timer.Period = TriggerTime;
}
--
2.25.1
next prev parent reply other threads:[~2022-09-21 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 2:10 [PATCH v1 0/1] MdeModulePkg/Core: Fix the potential hang of calling SetTimer Ying-Tsun Huang
2022-09-21 2:10 ` Ying-Tsun Huang [this message]
2022-09-21 16:35 ` [edk2-devel] [PATCH v1 1/1] " Michael D Kinney
-- strict thread matches above, loose matches on Subject: below --
2022-09-21 2:48 [PATCH v1 0/1] " ying-tsun.huang
2022-09-21 2:49 ` [PATCH v1 1/1] " Ying-Tsun Huang
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=20220921021023.4009-2-ying-tsun.huang@amd.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