From: Masahiro Yamada <masahiroy@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH v2 3/4] scripts/misc-check: check missing #include <linux/export.h> when W=1
Date: Fri, 20 Jun 2025 01:13:28 +0900 [thread overview]
Message-ID: <CAK7LNARJdVRcUCKo2zEfJr_0Dc-1fzkjf01OsDpDQLH2+wZHCg@mail.gmail.com> (raw)
In-Reply-To: <20250619090100.39e37c5a@kernel.org>
On Fri, Jun 20, 2025 at 1:01 AM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Sun, 1 Jun 2025 22:31:29 +0900 Masahiro Yamada wrote:
> > The problem was described in commit 5b20755b7780 ("init: move THIS_MODULE
> > from <linux/export.h> to <linux/init.h>").
> >
> > To summarize it again here: <linux/export.h> is included by most C files,
> > even though only some of them actually export symbols. This is because
> > some headers, such as include/linux/{module.h,linkage}, needlessly
> > include <linux/export.h>.
> >
> > I have added a more detailed explanation in the comments of
> > scripts/misc-check.
> >
> > This problem will be fixed in two steps:
> >
> > 1. Add #include <linux/export.h> to C files that use EXPORT_SYMBOL()
> > 2. Remove #include <linux/export.h> from header files that do not use
> > EXPORT_SYMBOL()
> >
> > This commit addresses step 1; scripts/misc-check will warn about *.[ch]
> > files that use EXPORT_SYMBOL() but do not include <linux/export.h>.
> > This check is only triggered when the kernel is built with W=1.
> >
> > We need to fix 4000+ files. I hope others will help with this effort.
>
> IIUC you made the kernel spew nearly 5000 warnings on every W=1 build
> to "encourage" others to help fix a fairly innocuous problem.
> I appreciate the work that goes into separating the headers but it's
> hardly urgent enough to force others to scroll thru 5k warnings.
>
> Please LMK if I'm missing some context here, otherwise I think this is
> quite antisocial behavior, and the warnings should go back to W=2 until
> someone actually cares to fix most of them.
>
> Happy to hear from others.. CC: workflows
Please see commit a6a7946bd691940cfe7289ae6dfb1f077516df72
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2025-06-19 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250601133230.4085512-1-masahiroy@kernel.org>
[not found] ` <20250601133230.4085512-3-masahiroy@kernel.org>
2025-06-19 16:01 ` Jakub Kicinski
2025-06-19 16:13 ` Masahiro Yamada [this message]
2025-06-19 16:26 ` Jakub Kicinski
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=CAK7LNARJdVRcUCKo2zEfJr_0Dc-1fzkjf01OsDpDQLH2+wZHCg@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/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