qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2] hw/virtio/vhost-shadow-virtqueue: Silence GCC error "maybe-uninitialized"
Date: Sat, 10 Sep 2022 20:20:26 +0000	[thread overview]
Message-ID: <52E205FD-5EE7-4DF5-878F-693165AE049A@gmail.com> (raw)
In-Reply-To: <20220910151117.6665-1-shentey@gmail.com>

Am 10. September 2022 15:11:17 UTC schrieb Bernhard Beschow <shentey@gmail.com>:
>GCC issues a false positive warning, resulting in build failure with -Werror:
>
>  In file included from /usr/include/glib-2.0/glib.h:114,
>                   from src/include/glib-compat.h:32,
>                   from src/include/qemu/osdep.h:144,
>                   from ../src/hw/virtio/vhost-shadow-virtqueue.c:10:
>  In function ‘g_autoptr_cleanup_generic_gfree’,
>      inlined from ‘vhost_handle_guest_kick’ at ../src/hw/virtio/vhost-shadow-virtqueue.c:292:42:
>  /usr/include/glib-2.0/glib/glib-autocleanups.h:28:3: error: ‘elem’ may be used uninitialized [-Werror=maybe-uninitialized]
>     28 |   g_free (*pp);
>        |   ^~~~~~~~~~~~
>  ../src/hw/virtio/vhost-shadow-virtqueue.c: In function ‘vhost_handle_guest_kick’:
>  ../src/hw/virtio/vhost-shadow-virtqueue.c:292:42: note: ‘elem’ was declared here
>    292 |             g_autofree VirtQueueElement *elem;
>        |                                          ^~~~
>  cc1: all warnings being treated as errors
>
>There is actually no problem since "elem" is initialized in both branches.
>Silence the warning by initializig it with "NULL".
>
>$ gcc --version
>gcc (GCC) 12.2.0
>
>Fixes: 9c2ab2f1ec333be8614cc12272d4b91960704dbe ("vhost: stop transfer elem ownership in vhost_handle_guest_kick")
>Signed-off-by: Bernhard Beschow <shentey@gmail.com>

Forgot to add from v1:

Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

>---
> hw/virtio/vhost-shadow-virtqueue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/hw/virtio/vhost-shadow-virtqueue.c b/hw/virtio/vhost-shadow-virtqueue.c
>index e8e5bbc368..596d4434d2 100644
>--- a/hw/virtio/vhost-shadow-virtqueue.c
>+++ b/hw/virtio/vhost-shadow-virtqueue.c
>@@ -289,7 +289,7 @@ static void vhost_handle_guest_kick(VhostShadowVirtqueue *svq)
>         virtio_queue_set_notification(svq->vq, false);
> 
>         while (true) {
>-            g_autofree VirtQueueElement *elem;
>+            g_autofree VirtQueueElement *elem = NULL;
>             int r;
> 
>             if (svq->next_guest_avail_elem) {



  parent reply	other threads:[~2022-09-10 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 15:11 [PATCH v2] hw/virtio/vhost-shadow-virtqueue: Silence GCC error "maybe-uninitialized" Bernhard Beschow
2022-09-10 16:05 ` Richard Henderson
2022-09-10 20:20 ` Bernhard Beschow [this message]
2022-09-20  5:29 ` Bernhard Beschow
2022-09-27 22:08   ` B
2022-09-29 19:08 ` Laurent Vivier

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=52E205FD-5EE7-4DF5-878F-693165AE049A@gmail.com \
    --to=shentey@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).