qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH-for-5.2] hw/virtio/vhost-backend: Fix Coverity CID 1432871
Date: Mon, 2 Nov 2020 22:22:28 +0000	[thread overview]
Message-ID: <CAFEAcA8a3UEf_e4jvEdemidrQ7g=V6Ar1dYROQVU5VrsUijJ8Q@mail.gmail.com> (raw)
In-Reply-To: <20201102203609.2228309-1-philmd@redhat.com>

On Mon, 2 Nov 2020 at 20:36, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> Fix uninitialized value issues reported by Coverity:
>
>   Field 'msg.reserved' is uninitialized when calling write().
>
> Reported-by: Coverity (CID 1432864: UNINIT)
> Fixes: c471ad0e9bd ("vhost_net: device IOTLB support")
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
>  hw/virtio/vhost-backend.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/virtio/vhost-backend.c b/hw/virtio/vhost-backend.c
> index 88c8ecc9e03..222bbcc62de 100644
> --- a/hw/virtio/vhost-backend.c
> +++ b/hw/virtio/vhost-backend.c
> @@ -257,7 +257,7 @@ static int vhost_kernel_send_device_iotlb_msg(struct vhost_dev *dev,
>                                                struct vhost_iotlb_msg *imsg)
>  {
>      if (dev->backend_cap & (1ULL << VHOST_BACKEND_F_IOTLB_MSG_V2)) {
> -        struct vhost_msg_v2 msg;
> +        struct vhost_msg_v2 msg = {};
>
>          msg.type = VHOST_IOTLB_MSG_V2;
>          msg.iotlb = *imsg;
> @@ -267,7 +267,7 @@ static int vhost_kernel_send_device_iotlb_msg(struct vhost_dev *dev,
>              return -EFAULT;
>          }
>      } else {
> -        struct vhost_msg msg;
> +        struct vhost_msg msg = {};
>
>          msg.type = VHOST_IOTLB_MSG;
>          msg.iotlb = *imsg;

Coverity didn't mind about the struct vhost_msg because
it doesn't have a 'reserved' field like vhost_msg_v2; but it
doesn't hurt to initialize it and it makes the two parts of
the function consistent, which is good.

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

thanks
-- PMM


      reply	other threads:[~2020-11-02 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 20:36 [PATCH-for-5.2] hw/virtio/vhost-backend: Fix Coverity CID 1432871 Philippe Mathieu-Daudé
2020-11-02 22:22 ` 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='CAFEAcA8a3UEf_e4jvEdemidrQ7g=V6Ar1dYROQVU5VrsUijJ8Q@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mst@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).