summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2026-06-18 16:29:43 +0200
committerKees Cook <kees@kernel.org>2026-09-02 20:34:42 -0700
commitff936b726c981e362f02755b6417654dc4ef297a (patch)
treeebc437886c5fcceaa57bc70b3749c3f84015d3ac /scripts/Makefile.thinlto
parentb74dc82a3b289b872eb4ceaa2a3528e9d9b53931 (diff)
downloadlinux-next-ff936b726c981e362f02755b6417654dc4ef297a.tar.gz
linux-next-ff936b726c981e362f02755b6417654dc4ef297a.zip
KMSAN: fix memset() when using fortify-source, again
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 Commit 78a498c3a227 already tried to address this, but this seems to only have worked for memcpy() and memmove() but not memset(), which is still lacking the macro definition when KMSAN is enabled. Remove the incorrect #ifndef check around the memset() macro. Fixes: ff901d80fff6 ("x86: kmsan: use __msan_ string functions where possible.") Fixes: 78a498c3a227 ("x86: fortify: kmsan: fix KMSAN fortify builds") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Link: https://patch.msgid.link/20260618142951.1739694-1-arnd@kernel.org Signed-off-by: Kees Cook <kees@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions