From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zhang, Chao B" <chao.b.zhang@intel.com>
Subject: Re: [PATCH] SecurityPkg Tcg2Dxe: ASSERT to ensure 'VarData' is not NULL
Date: Mon, 21 Nov 2016 07:57:19 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C50386D8129@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1479714790-8016-1-git-send-email-hao.a.wu@intel.com>
Reviewed-by: jiewen.yao@intel.com
> -----Original Message-----
> From: Wu, Hao A
> Sent: Monday, November 21, 2016 3:53 PM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>;
> Zhang, Chao B <chao.b.zhang@intel.com>
> Subject: [PATCH] SecurityPkg Tcg2Dxe: ASSERT to ensure 'VarData' is not
> NULL
>
> The logic in functions ReadAndMeasureVariable() and MeasureVariable()
> within Tcg2Dxe ensure that 'VarData' will not be NULL before calling
> TcgDxeHashLogExtendEvent() at line 1716.
>
> This commit adds ASSERT as warnings for the case that will not happen.
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Hao Wu <hao.a.wu@intel.com>
> ---
> SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c
> b/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c
> index f0545a6..6a350e2 100644
> --- a/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c
> +++ b/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c
> @@ -1713,6 +1713,7 @@ MeasureVariable (
> (UINT8*)VarLog
> );
> } else {
> + ASSERT (VarData != NULL);
> Status = TcgDxeHashLogExtendEvent (
> 0,
> (UINT8*)VarData,
> --
> 1.9.5.msysgit.0
next prev parent reply other threads:[~2016-11-21 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 7:53 [PATCH] SecurityPkg Tcg2Dxe: ASSERT to ensure 'VarData' is not NULL Hao Wu
2016-11-21 7:57 ` Yao, Jiewen [this message]
2016-11-22 1:29 ` Zhang, Chao B
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=74D8A39837DF1E4DA445A8C0B3885C50386D8129@shsmsx102.ccr.corp.intel.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