public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	edk2-devel@ml01.01.org, michael.d.kinney@intel.com,
	liming.gao@intel.com
Subject: Re: [PATCH] MdePkg/BaseMemoryLibOptDxe: check for zero length in ZeroMem ()
Date: Thu, 3 Nov 2016 18:38:36 +0100	[thread overview]
Message-ID: <35e6e483-afcf-b735-c3ef-55236ac83423@redhat.com> (raw)
In-Reply-To: <1478194274-16524-1-git-send-email-ard.biesheuvel@linaro.org>

On 11/03/16 18:31, Ard Biesheuvel wrote:
> Unlike other string functions in this library, ZeroMem () does not
> return early when the length of the input buffer is 0. So add the
> same to ZeroMem () as well.
> 
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  MdePkg/Library/BaseMemoryLibOptDxe/ZeroMemWrapper.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MdePkg/Library/BaseMemoryLibOptDxe/ZeroMemWrapper.c b/MdePkg/Library/BaseMemoryLibOptDxe/ZeroMemWrapper.c
> index 2a0a038fd6c5..fbc2f5742c8c 100644
> --- a/MdePkg/Library/BaseMemoryLibOptDxe/ZeroMemWrapper.c
> +++ b/MdePkg/Library/BaseMemoryLibOptDxe/ZeroMemWrapper.c
> @@ -46,6 +46,10 @@ ZeroMem (
>    IN UINTN  Length
>    )
>  {
> +  if (Length == 0) {
> +    return Buffer;
> +  }
> +
>    ASSERT (!(Buffer == NULL && Length > 0));
>    ASSERT (Length <= (MAX_ADDRESS - (UINTN)Buffer + 1));
>    return InternalMemZeroMem (Buffer, Length);
> 

1. Why is this necessary?

2. After the new check, Length is guaranteed to be positive. The first
ASSERT() should be updated (simplified), I think:

  ASSERT (Buffer != NULL);

Thanks
Laszlo


  reply	other threads:[~2016-11-03 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 17:31 [PATCH] MdePkg/BaseMemoryLibOptDxe: check for zero length in ZeroMem () Ard Biesheuvel
2016-11-03 17:38 ` Laszlo Ersek [this message]
2016-11-03 18:05   ` Ard Biesheuvel
2016-11-03 18:10     ` Laszlo Ersek
2016-11-03 17:38 ` Carsey, Jaben

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=35e6e483-afcf-b735-c3ef-55236ac83423@redhat.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