From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nathan Chancellor" <nathan@kernel.org>
Cc: "Kees Cook" <keescook@chromium.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Steffen Klassert" <steffen.klassert@secunet.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Leon Romanovsky" <leon@kernel.org>, "Lin Ma" <linma@zju.edu.cn>,
"Simon Horman" <horms@kernel.org>,
"Breno Leitao" <leitao@debian.org>,
"Tobias Brunner" <tobias@strongswan.org>,
"Raed Salem" <raeds@nvidia.com>, Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] [RFC] xfrm: work around a clang-19 fortifiy-string false-positive
Date: Thu, 11 Apr 2024 13:35:05 +0200 [thread overview]
Message-ID: <773febee-ace3-4ad6-8ff6-04563dbbb759@app.fastmail.com> (raw)
In-Reply-To: <20240410174540.GB3649628@dev-arch.thelio-3990X>
On Wed, Apr 10, 2024, at 19:45, Nathan Chancellor wrote:
> Unfortunately, I have no idea why it is complaining nor why your patch
> resolves it but the combination of FORTIFY_SOURCE and KASAN certainly
> seems like a reasonable place to start looking. I will see if I can come
> up with a smaller reproducer to see if it becomes more obvious why this
> code triggers this warning.
I know at least why my patch avoids the warning -- it removes the
call to memset() that contains the check. Unfortunately that still
doesn't explain what caused it.
Arnd
next prev parent reply other threads:[~2024-04-11 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 20:26 [PATCH] [RFC] xfrm: work around a clang-19 fortifiy-string false-positive Arnd Bergmann
2024-02-16 20:42 ` Nathan Chancellor
2024-02-16 21:19 ` Kees Cook
2024-04-08 7:06 ` Arnd Bergmann
2024-04-09 16:15 ` Nathan Chancellor
2024-04-09 19:41 ` Arnd Bergmann
2024-04-10 17:45 ` Nathan Chancellor
2024-04-11 11:35 ` Arnd Bergmann [this message]
2024-04-12 21:21 ` Nathan Chancellor
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=773febee-ace3-4ad6-8ff6-04563dbbb759@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=steffen.klassert@secunet.com \
--cc=tobias@strongswan.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).