From: "Sergei Dmitrouk" <sergei@posteo.net>
To: devel@edk2.groups.io, jiewen.yao@intel.com
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
"Lu, XiaoyuX" <xiaoyux.lu@intel.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 3/3] CryptoPkg/BaseCryptLib: Fix possible uninitialized use
Date: Sat, 15 May 2021 13:00:41 +0000 [thread overview]
Message-ID: <20210515130041.GA6005@zx-spectrum> (raw)
In-Reply-To: <PH0PR11MB48856A6A912B87238B33D4398C2F9@PH0PR11MB4885.namprd11.prod.outlook.com>
Hello Jiewen,
I get the error only for GCC49 and not for GCC5 toolchain. CI uses GCC5.
So I compared build commands and this seems to depend on LTO. Adding `-flto`
impedes compiler's ability to detect such simple issues.
I've found relevant bug report, there is even fix suggestion from last month:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90844
Regards,
Sergei
On Sat, May 15, 2021 at 12:30:44AM +0000, Yao, Jiewen wrote:
> Hi Sergei
> Thank you very much for the fix.
> Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
>
> I am a little surprised why it is not caught before. It is an obvious logic issue.
>
> Do you think we can do anything on CI, to catch it during pre-check-in in the future?
> I just feel it is burden to make it post-check-in fix.
>
>
> Thank you
> Yao Jiewen
>
> > -----Original Message-----
> > From: Sergei Dmitrouk <sergei@posteo.net>
> > Sent: Friday, May 14, 2021 8:17 PM
> > To: devel@edk2.groups.io
> > Cc: Yao, Jiewen <jiewen.yao@intel.com>; Wang, Jian J <jian.j.wang@intel.com>;
> > Lu, XiaoyuX <xiaoyux.lu@intel.com>; Jiang, Guomin <guomin.jiang@intel.com>
> > Subject: [PATCH v1 3/3] CryptoPkg/BaseCryptLib: Fix possible uninitialized use
> >
> > `Result` can be used uninitialized in both functions after following
> > either first or second `goto` statement.
> >
> > Cc: Jiewen Yao <jiewen.yao@intel.com>
> > Cc: Jian J Wang <jian.j.wang@intel.com>
> > Cc: Xiaoyu Lu <xiaoyux.lu@intel.com>
> > Cc: Guomin Jiang <guomin.jiang@intel.com>
> > Signed-off-by: Sergei Dmitrouk <sergei@posteo.net>
> > ---
> > CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPss.c | 1 +
> > CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPssSign.c | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPss.c
> > b/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPss.c
> > index 4009d37d5f91..0b2960f06c4c 100644
> > --- a/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPss.c
> > +++ b/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPss.c
> > @@ -82,6 +82,7 @@ RsaPssVerify (
> > EVP_PKEY_CTX *KeyCtx;
> > CONST EVP_MD *HashAlg;
> >
> > + Result = FALSE;
> > EvpRsaKey = NULL;
> > EvpVerifyCtx = NULL;
> > KeyCtx = NULL;
> > diff --git a/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPssSign.c
> > b/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPssSign.c
> > index b66b6f7296ad..ece765f9ae0a 100644
> > --- a/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPssSign.c
> > +++ b/CryptoPkg/Library/BaseCryptLib/Pk/CryptRsaPssSign.c
> > @@ -97,6 +97,7 @@ RsaPssSign (
> > EVP_PKEY_CTX *KeyCtx;
> > CONST EVP_MD *HashAlg;
> >
> > + Result = FALSE;
> > EvpRsaKey = NULL;
> > EvpVerifyCtx = NULL;
> > KeyCtx = NULL;
> > --
> > 2.17.6
next prev parent reply other threads:[~2021-05-15 13:00 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
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 ` Sergei Dmitrouk [this message]
2021-05-18 0:59 ` 回复: [edk2-devel] " 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=20210515130041.GA6005@zx-spectrum \
--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