qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	 Raphael Norwitz <raphael@enfabrica.net>,
	changpeng.liu@intel.com
Subject: Re: [PATCH] contrib/vhost-user-blk: fix overflowing expression
Date: Fri, 12 Jul 2024 16:44:29 +0100	[thread overview]
Message-ID: <CAFEAcA_vtekZr7aEuH_=HQMPSw2L4mD32f3+rUCr8mUHWjwYKw@mail.gmail.com> (raw)
In-Reply-To: <20240712153857.207440-1-sgarzare@redhat.com>

On Fri, 12 Jul 2024 at 16:39, Stefano Garzarella <sgarzare@redhat.com> wrote:
>
> Coverity reported:
>
>   >>>     CID 1549454:  Integer handling issues  (OVERFLOW_BEFORE_WIDEN)
>   >>>     Potentially overflowing expression
>           "le32_to_cpu(desc->num_sectors) << 9" with type "uint32_t"
>           (32 bits, unsigned) is evaluated using 32-bit arithmetic, and
>           then used in a context that expects an expression of type
>           "uint64_t" (64 bits, unsigned).
>   199                               le32_to_cpu(desc->num_sectors) << 9 };
>
> Coverity noticed this issue after commit ab04420c3 ("contrib/vhost-user-*:
> use QEMU bswap helper functions"), but it was pre-existing and introduced
> from the beginning by commit caa1ee4313 ("vhost-user-blk: add
> discard/write zeroes features support").
>
> Explicitly cast the 32-bit value before the shift to fix this issue.
>
> Fixes: Coverity CID 1549454
> Fixes: 5ab04420c3 ("contrib/vhost-user-*: use QEMU bswap helper functions")
> Fixes: caa1ee4313 ("vhost-user-blk: add discard/write zeroes features support")
> Cc: changpeng.liu@intel.com
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
>  contrib/vhost-user-blk/vhost-user-blk.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/vhost-user-blk/vhost-user-blk.c b/contrib/vhost-user-blk/vhost-user-blk.c
> index 9492146855..6cc18a1c04 100644
> --- a/contrib/vhost-user-blk/vhost-user-blk.c
> +++ b/contrib/vhost-user-blk/vhost-user-blk.c
> @@ -196,7 +196,7 @@ vub_discard_write_zeroes(VubReq *req, struct iovec *iov, uint32_t iovcnt,
>      VubDev *vdev_blk = req->vdev_blk;
>      desc = buf;
>      uint64_t range[2] = { le64_to_cpu(desc->sector) << 9,
> -                          le32_to_cpu(desc->num_sectors) << 9 };
> +                          (uint64_t)le32_to_cpu(desc->num_sectors) << 9 };
>      if (type == VIRTIO_BLK_T_DISCARD) {
>          if (ioctl(vdev_blk->blk_fd, BLKDISCARD, range) == 0) {
>              g_free(buf);
> --

Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

thanks
-- PMM


      reply	other threads:[~2024-07-12 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 15:38 [PATCH] contrib/vhost-user-blk: fix overflowing expression Stefano Garzarella
2024-07-12 15:44 ` Peter Maydell [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-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='CAFEAcA_vtekZr7aEuH_=HQMPSw2L4mD32f3+rUCr8mUHWjwYKw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=changpeng.liu@intel.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael@enfabrica.net \
    --cc=sgarzare@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).