From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: Hao A Wu <hao.a.wu@intel.com>, Ray Ni <ray.ni@intel.com>,
Leif Lindholm <leif@nuviainc.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg AtaAtapiPassThru: Skip the potential NULL pointer access
Date: Tue, 23 Nov 2021 06:10:14 -0700 [thread overview]
Message-ID: <680de582-f33a-edd3-afbc-f9aafd05595d@nuviainc.com> (raw)
In-Reply-To: <20211116025328.1604-1-gaoliming@byosoft.com.cn>
Acked-by: Rebecca Cran <rebecca@nuviainc.com>
I've confirmed that this patch fixes the exception I was seeing when
running the DEBUG build of SbsaQemu.
--
Rebecca Cran
On 11/15/21 7:53 PM, gaoliming wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3732
> Recent change c974257821208fc6191779d1ddea918499f165b8 exposes this potential issue.
>
> Signed-off-by: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> ---
> MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> index 7626bac38d..bda900a161 100644
> --- a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> +++ b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> @@ -885,6 +885,13 @@ AhciPrintStatusBlock (
> IN UINT32 DebugLevel
> )
> {
> + //
> + // Skip NULL pointer
> + //
> + if (AtaStatusBlock == NULL) {
> + return;
> + }
> +
> //
> // Only print status and error since we have all of the rest printed as
> // a part of command block print.
next prev parent reply other threads:[~2021-11-23 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 2:53 [PATCH] MdeModulePkg AtaAtapiPassThru: Skip the potential NULL pointer access gaoliming
2021-11-16 3:48 ` [edk2-devel] " Wu, Hao A
2021-11-23 13:10 ` Rebecca Cran [this message]
2021-11-23 13:19 ` edk2-stable202111 " Leif Lindholm
2021-11-24 6:17 ` 回复: " gaoliming
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=680de582-f33a-edd3-afbc-f9aafd05595d@nuviainc.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