linux-kernel - Re: [PATCH v2] x86/Kconfig: Fix allyesconfig

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20250416170359.a0267b77d3db85ff6d5f8ac0@linux-foundation.org>
Date: Wed, 16 Apr 2025 17:03:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko
 <glider@...gle.com>, Andrey Konovalov <andreyknvl@...il.com>, Dmitry Vyukov
 <dvyukov@...gle.com>, Vincenzo Frascino <vincenzo.frascino@....com>,
 kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org, Linus Torvalds
 <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2] x86/Kconfig: Fix allyesconfig

On Wed, 16 Apr 2025 16:05:59 -0700 Guenter Roeck <linux@...ck-us.net> wrote:

> 64-bit allyesconfig builds fail with
> 
> x86_64-linux-ld: kernel image bigger than KERNEL_IMAGE_SIZE
> 
> Bisect points to commit 6f110a5e4f99 ("Disable SLUB_TINY for build
> testing") as the responsible commit. Reverting that patch does indeed
> fix the problem. Further analysis shows that disabling SLUB_TINY enables
> KASAN, and that KASAN is responsible for the image size increase.
> 
> Solve the build problem by disabling KASAN for test builds.
> 

Excluding KASAN from COMPILE_TEST builds is regrettable.

Can we address this some other way?  One way might be to alter or
disable the KERNEL_IMAGE_SIZE check if COMPILE_TEST?  That will be sad
for anyone who tries to boot a COMPILE_TEST kernel, but who the heck
does that?