From: Stefano Garzarella <sgarzare@redhat.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Bryan Tan <bryan-bt.tan@broadcom.com>,
Vishnu Dasa <vishnu.dasa@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Simon Horman <horms@kernel.org>,
HarshaVardhana S A <harshavardhana.sa@broadcom.com>,
Bobby Eshleman <bobbyeshleman@meta.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org
Subject: Re: [PATCH] vmw_vsock: bypass false-positive Wnonnull warning with gcc-16
Date: Wed, 4 Feb 2026 12:29:44 +0100 [thread overview]
Message-ID: <aYMqw2HbtKi50b1e@sgarzare-redhat> (raw)
In-Reply-To: <20260203163406.2636463-1-arnd@kernel.org>
On Tue, Feb 03, 2026 at 05:34:00PM +0100, Arnd Bergmann wrote:
>From: Arnd Bergmann <arnd@arndb.de>
>
>The gcc-16.0.1 snapshot produces a false-positive warning that turns
>into a build failure with CONFIG_WERROR:
>
>In file included from arch/x86/include/asm/string.h:6,
> from net/vmw_vsock/vmci_transport.c:10:
>In function 'vmci_transport_packet_init',
> inlined from '__vmci_transport_send_control_pkt.constprop' at net/vmw_vsock/vmci_transport.c:198:2:
>arch/x86/include/asm/string_32.h:150:25: error: argument 2 null where non-null expected because argument 3 is nonzero [-Werror=nonnull]
> 150 | #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
>net/vmw_vsock/vmci_transport.c:164:17: note: in expansion of macro 'memcpy'
> 164 | memcpy(&pkt->u.wait, wait, sizeof(pkt->u.wait));
> | ^~~~~~
>arch/x86/include/asm/string_32.h:150:25: note: in a call to built-in function '__builtin_memcpy'
>net/vmw_vsock/vmci_transport.c:164:17: note: in expansion of macro 'memcpy'
> 164 | memcpy(&pkt->u.wait, wait, sizeof(pkt->u.wait));
> | ^~~~~~
>
>This seems relatively harmless, and it so far the only instance of this
>warning I have found. The __vmci_transport_send_control_pkt function
>is called either with wait=NULL or with one of the type values that
>pass 'wait' into memcpy() here, but not from the same caller.
>
>Replacing the memcpy with a struct assignment is otherwise the same
>but avoids the warning.
>
>Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>---
> net/vmw_vsock/vmci_transport.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Not sure if it's net or net-next material, maybe net to avoid the
warning/error on v6.19 too ?
Anyway LGTM and thanks for the fix!
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
>
>diff --git a/net/vmw_vsock/vmci_transport.c b/net/vmw_vsock/vmci_transport.c
>index 00f6bbdb035a..a64522be1bad 100644
>--- a/net/vmw_vsock/vmci_transport.c
>+++ b/net/vmw_vsock/vmci_transport.c
>@@ -161,7 +161,7 @@ vmci_transport_packet_init(struct vmci_transport_packet *pkt,
>
> case VMCI_TRANSPORT_PACKET_TYPE_WAITING_READ:
> case VMCI_TRANSPORT_PACKET_TYPE_WAITING_WRITE:
>- memcpy(&pkt->u.wait, wait, sizeof(pkt->u.wait));
>+ pkt->u.wait = *wait;
> break;
>
> case VMCI_TRANSPORT_PACKET_TYPE_REQUEST2:
>--
>2.39.5
>
next prev parent reply other threads:[~2026-02-04 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 16:34 [PATCH] vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 Arnd Bergmann
2026-02-03 18:17 ` Bobby Eshleman
2026-02-04 11:29 ` Stefano Garzarella [this message]
2026-02-05 2:41 ` Jakub Kicinski
2026-02-04 14:35 ` Bryan Tan
2026-02-05 2:50 ` patchwork-bot+netdevbpf
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=aYMqw2HbtKi50b1e@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bobbyeshleman@meta.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harshavardhana.sa@broadcom.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.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