[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250413022240.GB3020916@ax162>
Date: Sat, 12 Apr 2025 21:22:40 -0500
From: Nathan Chancellor <nathan@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Peter Zijlstra <peterz@...radead.org>, Arnd Bergmann <arnd@...db.de>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Arnd Bergmann <arnd@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>, Rae Moar <rmoar@...gle.com>,
Shuah Khan <skhan@...uxfoundation.org>,
Sergio González Collado <sergio.collado@...il.com>,
David Gow <davidgow@...gle.com>,
Nicolas Schier <nicolas.schier@...ux.dev>,
Mostafa Saleh <smostafa@...gle.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts/mksysmap: skip objtool __pfx_ symbols
On Sat, Apr 12, 2025 at 10:22:18AM -0400, Steven Rostedt wrote:
> Even after removing that test, my allyesconfig still fails to build with:
>
> ld.lld: error: kernel image bigger than KERNEL_IMAGE_SIZE
> ld.lld: error: kernel image bigger than KERNEL_IMAGE_SIZE
> ld.lld: error: kernel image bigger than KERNEL_IMAGE_SIZE
>
> I guess I'll just have to remove allyesconfig from my test suite. I
> still do allmodconfig which appears to still work. At least that will
> shorten my test suite time as allyesconfig takes around a half hour to
> complete.
I noticed this from our CI too (I don't see the actual error there as
the build just times out before it can get there but I can see it
locally with all the same tools) and it seems like it is caused by
Linus's commit 6f110a5e4f99 ("Disable SLUB_TINY for build testing"),
which causes CONFIG_KASAN to be enabled for all{mod,yes}config again,
which contributes to blowing out the kernel size. I see this with both
GCC and Clang so I guess we will pursue the same solution and just stop
testing allyesconfig (unless we wanted to stop turning on KASAN for
all*config).
Cheers,
Nathan
Powered by blists - more mailing lists