From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christophe Marie Francois Dupont de Dinechin <cdupontd@redhat.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
trivial@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
virtualization@lists.linux-foundation.org,
Ben Segall <bsegall@google.com>, Ingo Molnar <mingo@redhat.com>,
Mel Gorman <mgorman@suse.de>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Christophe de Dinechin <dinechin@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH 3/3] virtio-pci: Use cpumask_available to fix compilation error
Date: Thu, 28 Apr 2022 07:06:35 -0400 [thread overview]
Message-ID: <20220428070620-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <3D264F7F-624D-4E9D-A139-F1DB0CC6045C@redhat.com>
On Thu, Apr 28, 2022 at 11:48:01AM +0200, Christophe Marie Francois Dupont de Dinechin wrote:
>
>
> > On 15 Apr 2022, at 10:48, Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Thu, Apr 14, 2022 at 05:08:55PM +0200, Christophe de Dinechin wrote:
> >> With GCC 12 and defconfig, we get the following error:
> >>
> >> | CC drivers/virtio/virtio_pci_common.o
> >> | drivers/virtio/virtio_pci_common.c: In function ‘vp_del_vqs’:
> >> | drivers/virtio/virtio_pci_common.c:257:29: error: the comparison will
> >> | always evaluate as ‘true’ for the pointer operand in
> >> | ‘vp_dev->msix_affinity_masks + (sizetype)((long unsigned int)i * 8)’
> >> | must not be NULL [-Werror=address]
> >> | 257 | if (vp_dev->msix_affinity_masks[i])
> >> | | ^~~~~~
> >>
> >> This happens in the case where CONFIG_CPUMASK_OFFSTACK is not defined,
> >> since we typedef cpumask_var_t as an array. The compiler is essentially
> >> complaining that an array pointer cannot be NULL. This is not a very
> >> important warning, but there is a function called cpumask_available that
> >> seems to be defined just for that case, so the fix is easy.
> >>
> >> Signed-off-by: Christophe de Dinechin <christophe@dinechin.org>
> >> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
> >
> > There was an alternate patch proposed for this by
> > Murilo Opsfelder Araujo. What do you think about that approach?
>
> I responded on the other thread, but let me share the response here:
>
> [to muriloo@linux.ibm.com]
> Apologies for the delay in responding, broken laptop…
>
> In the case where CONFIG_CPUMASK_OFFSTACK is not defined, we have:
>
> typedef struct cpumask cpumask_var_t[1];
>
> So that vp_dev->msix_affinity_masks[i] is statically not null (that’s the warning)
> but also a static pointer, so not kfree-safe IMO.
Not sure I understand what you are saying here.
> >
> >
> >> ---
> >> drivers/virtio/virtio_pci_common.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/virtio/virtio_pci_common.c b/drivers/virtio/virtio_pci_common.c
> >> index d724f676608b..5c44a2f13c93 100644
> >> --- a/drivers/virtio/virtio_pci_common.c
> >> +++ b/drivers/virtio/virtio_pci_common.c
> >> @@ -254,7 +254,7 @@ void vp_del_vqs(struct virtio_device *vdev)
> >>
> >> if (vp_dev->msix_affinity_masks) {
> >> for (i = 0; i < vp_dev->msix_vectors; i++)
> >> - if (vp_dev->msix_affinity_masks[i])
> >> + if (cpumask_available(vp_dev->msix_affinity_masks[i]))
> >> free_cpumask_var(vp_dev->msix_affinity_masks[i]);
> >> }
> >>
> >> --
> >> 2.35.1
> >
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-04-28 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220414150855.2407137-1-dinechin@redhat.com>
[not found] ` <20220414150855.2407137-2-dinechin@redhat.com>
2022-04-14 15:21 ` [PATCH 1/3] sched/headers: Fix compilation error with GCC 12 Peter Zijlstra
2022-04-14 20:30 ` Andrew Morton
2022-04-17 15:52 ` Peter Zijlstra
2022-04-20 18:45 ` Kees Cook
2022-04-21 7:32 ` Peter Zijlstra
2022-04-17 13:27 ` David Laight
[not found] ` <5AEAD35F-10E2-41A3-8269-E8358160D33B@dinechin.org>
2022-05-19 11:16 ` Peter Zijlstra
[not found] ` <20220414150855.2407137-3-dinechin@redhat.com>
2022-04-14 15:23 ` [PATCH 2/3] nodemask.h: Fix compilation error with GCC12 Peter Zijlstra
[not found] ` <20220414150855.2407137-4-dinechin@redhat.com>
2022-04-15 8:48 ` [PATCH 3/3] virtio-pci: Use cpumask_available to fix compilation error Michael S. Tsirkin
2022-04-28 9:48 ` Christophe Marie Francois Dupont de Dinechin
2022-04-28 11:06 ` Michael S. Tsirkin [this message]
2022-05-15 21:24 ` [PATCH 0/3] trivial: Fix several compilation errors/warnings with GCC12 Davidlohr Bueso
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=20220428070620-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=cdupontd@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=dinechin@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=muriloo@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=thunder.leizhen@huawei.com \
--cc=trivial@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=virtualization@lists.linux-foundation.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).