public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ShellPkg/Shell: Avoid potential null pointer deference
Date: Tue, 28 Mar 2017 03:09:37 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A0931C8812F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20170328022700.132784-1-ruiyu.ni@intel.com>

Reviewed-by: Hao Wu <hao.a.wu@intel.com>

Best Regards,
Hao Wu


> -----Original Message-----
> From: Ni, Ruiyu
> Sent: Tuesday, March 28, 2017 10:27 AM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A
> Subject: [PATCH] ShellPkg/Shell: Avoid potential null pointer deference
> 
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> ---
>  ShellPkg/Application/Shell/Shell.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/ShellPkg/Application/Shell/Shell.c
> b/ShellPkg/Application/Shell/Shell.c
> index dfcbfb8..af8e523 100644
> --- a/ShellPkg/Application/Shell/Shell.c
> +++ b/ShellPkg/Application/Shell/Shell.c
> @@ -1162,6 +1162,12 @@ LocateStartupScript (
>    MapName = ShellInfoObject.NewEfiShellProtocol->GetMapFromDevicePath
> (&ImageDevicePath);
>    if (MapName != NULL) {
>      StartupScriptPath = StrnCatGrow (&StartupScriptPath, &Size, MapName, 0);
> +    if (StartupScriptPath == NULL) {
> +      //
> +      // Do not locate the startup script in sys path when out of resource.
> +      //
> +      return NULL;
> +    }
>      TempSpot = StrStr (StartupScriptPath, L";");
>      if (TempSpot != NULL) {
>        *TempSpot = CHAR_NULL;
> --
> 2.9.0.windows.1



      reply	other threads:[~2017-03-28  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  2:27 [PATCH] ShellPkg/Shell: Avoid potential null pointer deference Ruiyu Ni
2017-03-28  3:09 ` Wu, Hao A [this message]

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=B80AF82E9BFB8E4FBD8C89DA810C6A0931C8812F@SHSMSX104.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