From: "Ni, Ray" <ray.ni@intel.com>
To: Sergei Dmitrouk <sergei@posteo.net>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>, "Wu, Hao A" <hao.a.wu@intel.com>
Subject: Re: [PATCH v1 2/3] MdeModulePkg/PciBusDxe: Fix possible uninitialized use
Date: Mon, 17 May 2021 02:05:39 +0000 [thread overview]
Message-ID: <CO1PR11MB49300DC4CDBF6750CD641B2E8C2D9@CO1PR11MB4930.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210514121714.17312-3-sergei@posteo.net>
How about below fix? I think it might be simpler to understand and doesn't introduce unnecessary logic to handle impossible case:
if (ResizableBarOp == PciResizableBarMax) {
Bit = HighBitSet64(Capabilities);
} else {
ASSERT (ResizableBarOp == PciResizableBarMin);
Bit = LowBitSet64(Capabilities);
}
> -----Original Message-----
> From: Sergei Dmitrouk <sergei@posteo.net>
> Sent: Friday, May 14, 2021 8:17 PM
> To: devel@edk2.groups.io
> Cc: Wang, Jian J <jian.j.wang@intel.com>; Wu, Hao A <hao.a.wu@intel.com>;
> Ni, Ray <ray.ni@intel.com>
> Subject: [PATCH v1 2/3] MdeModulePkg/PciBusDxe: Fix possible uninitialized
> use
>
> If the function gets invalid value for the `ResizableBarOp` parameter
> and asserts are disabled, `Bit` can be used uninitialized.
>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Signed-off-by: Sergei Dmitrouk <sergei@posteo.net>
> ---
> MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c
> b/MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c
> index 6bba28367165..de601713a53b 100644
> --- a/MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c
> +++ b/MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c
> @@ -1781,6 +1781,11 @@ PciProgramResizableBar (
> } else if (ResizableBarOp == PciResizableBarMin) {
> Bit = LowBitSet64(Capabilities);
> } else {
> + //
> + // Set Bit to avoid uninitialized use when built without assertions.
> + //
> + Bit = 0;
> +
> ASSERT ((ResizableBarOp == PciResizableBarMax) || (ResizableBarOp ==
> PciResizableBarMin));
> }
>
> --
> 2.17.6
next prev parent reply other threads:[~2021-05-17 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 12:17 [PATCH v1 0/3] Fix possible uninitialized uses Sergei Dmitrouk
2021-05-14 12:17 ` [PATCH v1 1/3] ShellPkg/HttpDynamicCommand: Fix possible uninitialized use Sergei Dmitrouk
2021-05-14 12:17 ` [PATCH v1 2/3] MdeModulePkg/PciBusDxe: " Sergei Dmitrouk
2021-05-17 2:05 ` Ni, Ray [this message]
2021-05-17 16:22 ` [edk2-devel] " Sergei Dmitrouk
2021-05-18 8:01 ` Wu, Hao A
2021-05-14 12:17 ` [PATCH v1 3/3] CryptoPkg/BaseCryptLib: " Sergei Dmitrouk
2021-05-15 0:30 ` Yao, Jiewen
2021-05-15 13:00 ` [edk2-devel] " Sergei Dmitrouk
2021-05-18 0:59 ` 回复: " gaoliming
2021-05-18 7:26 ` Ard Biesheuvel
2021-05-18 7:36 ` Wang, Jian J
2021-05-19 0:59 ` 回复: " gaoliming
2021-05-19 1:03 ` Yao, Jiewen
2021-05-18 16:02 ` 回复: " Sergei Dmitrouk
2021-05-19 1:26 ` 回复: " 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=CO1PR11MB49300DC4CDBF6750CD641B2E8C2D9@CO1PR11MB4930.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