From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Damian Tometzki <damian@riscv-rocks.de>,
Masahiro Yamada <masahiroy@kernel.org>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.15-rc1
Date: Mon, 7 Apr 2025 06:41:09 +1000 [thread overview]
Message-ID: <20250407064109.5b441f5e@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wh-k04MsoEC0SGKff2Snm6bBF_e+0pHOKwaWv4umZ_SnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
Hi Linus,
On Sun, 6 Apr 2025 09:50:05 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Sat, 5 Apr 2025 at 22:43, Damian Tometzki <damian@riscv-rocks.de> wrote:
> >
> > i got the following error after this pull request.
> >
> > MODPOST Module.symvers
> > ERROR: modpost: missing MODULE_DESCRIPTION() in lib/tests/slub_kunit.o
> > make[3]: *** [/home/damian/kernel/linux/scripts/Makefile.modpost:147: Module.symvers] Error 1
> > make[2]: *** [/home/damian/kernel/linux/Makefile:1956: modpost] Error 2
> > make[1]: *** [/home/damian/kernel/linux/Makefile:248: __sub-make] Error 2
> > make[1]: Leaving directory '/home/damian/kernel/build'
> > make: *** [Makefile:248: __sub-make] Error 2
>
> Bah. And the reason it doesn't show up in my normal build tests is
> that my 'allmodconfig' tests end up picking up SLUB_TINY - which
> disables a lot of slub cases, including this test.
>
> And my normal non-allmodconfig tests don't enable SLUB_KUNIT_TEST.
>
> That said, I'm not sure if making it a hard error was a good idea in
> the first place. It *used* to be just a warning, and it used to be
> enabled only with 'extra_warn'.
>
> So switching it on to always warn was probably a good idea, but then
> also making it a hard error may have been a bit excessive.
>
> In related news - I also wonder whether SLUB_TINY should just be
> turned off for COMPILE_TEST. It's not a very interesting config option
> to test for, and it disables much more code than it enables [*].
>
> Testing this without SLUB_TINY, I see that it *also* triggers this one:
>
> ERROR: modpost: missing MODULE_DESCRIPTION() in mm/kasan/kasan_test.o
>
> so the claim in commit 6c6c1fc09de3 ("modpost: require a
> MODULE_DESCRIPTION()") that "all known instances of this issue have
> been fixed" is clearly wrong.
>
> For all we know, there are lots of other cases like this that just
> never got tested with W=1 at all.
>
> I think I'll downgrade the error() to a warn() again, and make
> SLUB_TINY depend on !COMPILE_TEST.
>
> And I'm not even convinced we should require module descriptions for
> silly test modules, but whatever.
>
> We'll see if something else pops up, but making the lack of a module
> description a fatal error was clearly not right as-is.
https://lore.kernel.org/lkml/20250324103048.3d8230f9@canb.auug.org.au/
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-06 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 22:04 [GIT PULL] Kbuild updates for v6.15-rc1 Masahiro Yamada
2025-04-05 22:50 ` pr-tracker-bot
2025-04-06 5:43 ` Damian Tometzki
2025-04-06 16:50 ` Linus Torvalds
2025-04-06 20:41 ` Stephen Rothwell [this message]
2025-04-07 8:34 ` Vlastimil Babka
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=20250407064109.5b441f5e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=damian@riscv-rocks.de \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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