linux-kernel - Re: [PATCH] KMSAN: Restore dynamic check for '-fsanitize=kernel-memory'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251023230130.GA3006010@ax162>
Date: Fri, 24 Oct 2025 00:01:30 +0100
From: Nathan Chancellor <nathan@...nel.org>
To: Alexander Potapenko <glider@...gle.com>, Marco Elver <elver@...gle.com>,
	Dmitry Vyukov <dvyukov@...gle.com>
Cc: Nicolas Schier <nsc@...nel.org>, Kees Cook <kees@...nel.org>,
	kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
	llvm@...ts.linux.dev, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] KMSAN: Restore dynamic check for
 '-fsanitize=kernel-memory'

On Thu, Oct 23, 2025 at 11:54:35PM +0100, Nathan Chancellor wrote:
> On Thu, 23 Oct 2025 21:01:29 +0200, Nathan Chancellor wrote:
> > Commit 5ff8c11775c7 ("KMSAN: Remove tautological checks") changed
> > CONFIG_HAVE_KMSAN_COMPILER from a dynamic check for
> > '-fsanitize=kernel-memory' to just being true for CONFIG_CC_IS_CLANG.
> > This missed the fact that not all architectures supported
> > '-fsanitize=kernel-memory' at the same time. For example, SystemZ / s390
> > gained support for KMSAN in clang-18 [1], so builds with clang-15
> > through clang-17 can select KMSAN but they error with:
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/1] KMSAN: Restore dynamic check for '-fsanitize=kernel-memory'
>       https://git.kernel.org/kbuild/c/a16758f0142ab

Whoops, sent the applied message for the wrong change... This is going
to be in kbuild-fixes as https://git.kernel.org/kbuild/c/3423b2866797c
for -next testing but I will adjust it for any tags I receive in the
next few days.

Cheers,
Nathan