From: Willem de Bruijn <willemdebruijn.kernel@gmail•com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail•com>,
Ankit Khushwaha <ankitkhushwaha.linux@gmail•com>,
Willem de Bruijn <willemdebruijn.kernel@gmail•com>
Cc: Jason Xing <kernelxing@tencent•com>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>,
Paolo Abeni <pabeni@redhat•com>,
Simon Horman <horms@kernel•org>, Shuah Khan <shuah@kernel•org>,
netdev@vger•kernel.org, linux-kselftest@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH] selftests/net: initialize char variable to null
Date: Tue, 25 Nov 2025 11:14:50 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.2f2a6f8b32ff1@gmail.com> (raw)
In-Reply-To: <willemdebruijn.kernel.10c7edf4c3dd1@gmail.com>
Willem de Bruijn wrote:
> Ankit Khushwaha wrote:
> > On Mon, Nov 24, 2025 at 01:15:33PM -0500, Willem de Bruijn wrote:
> > > This does not reproduce for me.
> > >
> > > Can you share the full clang command that V=1 outputs, as well as the
> > > output oof clang --version.
> >
> > Hi Willem,
> > I have added clang output in
> > https://gist.github.com/ankitkhushwaha/8e93e3d37917b3571a7ce0e9c9806f18
> >
> > Thanks,
> > Ankit
>
> I see. This is with clang-21. It did not trigger for me with clang-19.
>
> I was able to reproduce with Ubuntu 25.10.
>
> Okay, good to suppress these false positives with normal builds.
>
> Reviewed-by: Willem de Bruijn <willemb@google•com>
>
The patch status is already changes requested.
Please resubmit and target [PATCH net-next]
prev parent reply other threads:[~2025-11-25 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 16:13 [PATCH] selftests/net: initialize char variable to null Ankit Khushwaha
2025-11-24 17:46 ` Willem de Bruijn
2025-11-24 17:59 ` Ankit Khushwaha
2025-11-24 18:15 ` Willem de Bruijn
2025-11-25 4:33 ` Ankit Khushwaha
2025-11-25 16:04 ` Willem de Bruijn
2025-11-25 16:14 ` Willem de Bruijn [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=willemdebruijn.kernel.2f2a6f8b32ff1@gmail.com \
--to=willemdebruijn.kernel@gmail$(echo .)com \
--cc=ankitkhushwaha.linux@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kernelxing@tencent$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=shuah@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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