qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: avoid memcpy(dst, NULL, len)
Date: Tue, 13 Sep 2016 11:30:02 +0200	[thread overview]
Message-ID: <20160913093002.GA6021@noname.redhat.com> (raw)
In-Reply-To: <1473758138-19260-1-git-send-email-stefanha@redhat.com>

Am 13.09.2016 um 11:15 hat Stefan Hajnoczi geschrieben:
> Section "7.1.4 Use of library functions" in the C99 standard says:
> 
>   If an argument to a function has an invalid value (such as [...]
>   a null pointer [...]) [...] the behavior is undefined.
> 
> Additionally the "searching and sorting" functions are specified as
> requiring valid pointer values as described in 7.1.4.
> 
> This patch fixes the following static analyzer errors:

"sanitizer", not "static analyzer"

>   block/qcow2.c:1807:41: runtime error: null pointer passed as argument 2, which is declared to never be null
>   block/qcow2-cluster.c:86:26: runtime error: null pointer passed as argument 2, which is declared to never be null
> 
> Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  block/qcow2-cluster.c | 4 +++-
>  block/qcow2.c         | 5 ++++-
>  2 files changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
> index f941835..ab0dcdc 100644
> --- a/block/qcow2-cluster.c
> +++ b/block/qcow2-cluster.c
> @@ -83,7 +83,9 @@ int qcow2_grow_l1_table(BlockDriverState *bs, uint64_t min_size,
>      }
>      memset(new_l1_table, 0, align_offset(new_l1_size2, 512));
>  
> -    memcpy(new_l1_table, s->l1_table, s->l1_size * sizeof(uint64_t));
> +    if (s->l1_table) {
> +        memcpy(new_l1_table, s->l1_table, s->l1_size * sizeof(uint64_t));
> +    }

We could add 'else assert(s->l1_size == 0)' to make the intentions
clearer.  Or actually, maybe the simpler way would be to do
'if (s->l1_size)', then it's obvious that the skipped memcpy() wouldn't
do anything anyway.

>      /* write new table (align to cluster) */
>      BLKDBG_EVENT(bs->file, BLKDBG_L1_GROW_ALLOC_TABLE);
> diff --git a/block/qcow2.c b/block/qcow2.c
> index c079aa8..758a997 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -1804,7 +1804,10 @@ static size_t header_ext_add(char *buf, uint32_t magic, const void *s,
>          .magic  = cpu_to_be32(magic),
>          .len    = cpu_to_be32(len),
>      };
> -    memcpy(buf + sizeof(QCowExtension), s, len);
> +
> +    if (s) {
> +        memcpy(buf + sizeof(QCowExtension), s, len);
> +    }

Same thing here.

With or without the change:

Reviewed-by: Kevin Wolf <kwolf@redhat.com>

  reply	other threads:[~2016-09-13  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  9:15 [Qemu-devel] [PATCH] qcow2: avoid memcpy(dst, NULL, len) Stefan Hajnoczi
2016-09-13  9:30 ` Kevin Wolf [this message]
2016-09-13  9:56   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-09-13 13:14 ` [Qemu-devel] " Paolo Bonzini
2016-09-13 15:13 ` Eric Blake

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-all 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=20160913093002.GA6021@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).