From: Kees Cook <kees@kernel.org>
To: Alexander Potapenko <glider@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@kernel.org>
Cc: Kees Cook <kees@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
David Laight <david.laight.linux@gmail.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KMSAN: fix memset() when using fortify-source, again
Date: Wed, 2 Sep 2026 20:39:17 -0700 [thread overview]
Message-ID: <178840674549.2647132.11479583220926959631.b4-ty@kernel.org> (raw)
In-Reply-To: <20260618142951.1739694-1-arnd@kernel.org>
On Thu, 18 Jun 2026 16:29:43 +0200, Arnd Bergmann wrote:
> Both kmsan and fortify-source replace the memset function. When both
> are enabled at the same time, the kmsan version gets used, which triggers
> a warning about fortify-source being nonfunctional:
>
> warning: unsafe memset() usage lacked '__write_overflow' symbol in /home/arnd/arm-soc/lib/test_fortify/write_overflow-memset.c
> warning: unsafe memset() usage lacked '__write_overflow_field' symbol in /home/arnd/arm-soc/lib/test_fortify/write_overflow_field-memset.c
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] KMSAN: fix memset() when using fortify-source, again
https://git.kernel.org/kees/c/ff936b726c98
Take care,
--
Kees Cook
prev parent reply other threads:[~2026-09-03 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 14:29 Arnd Bergmann
2026-06-19 3:55 ` Kees Cook
2026-06-19 6:01 ` Arnd Bergmann
2026-09-03 3:39 ` Kees Cook [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=178840674549.2647132.11479583220926959631.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=glider@google.com \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®