From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH v2 4/4] scripts/misc-check: check unnecessary #include <linux/export.h> when W=1
Date: Sun, 1 Jun 2025 22:31:30 +0900 [thread overview]
Message-ID: <20250601133230.4085512-4-masahiroy@kernel.org> (raw)
In-Reply-To: <20250601133230.4085512-1-masahiroy@kernel.org>
Another issue with <linux/export.h> is that it is sometimes included
even when EXPORT_SYMBOL() is not used at all.
Some headers (e.g. include/linux/linkage.h>) cannot be fixed for now
for the reason described in the previous commit.
This commit adds a warning for *.c files that include <linux/export.h>
but do not use EXPORT_SYMBOL() when the kernel is built with W=1.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
eries-changes: 2
- Fix out-of-tree build
---
(no changes since v1)
scripts/misc-check | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/scripts/misc-check b/scripts/misc-check
index edc0e44d96de..f3b6bdce5fa2 100755
--- a/scripts/misc-check
+++ b/scripts/misc-check
@@ -51,5 +51,17 @@ check_missing_include_linux_export_h () {
xargs printf "%s: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing\n" >&2
}
+# If you do not use EXPORT_SYMBOL(), please do not include <linux/export.h>.
+# Currently, this is checked for *.c files, but not for *.h files, because some
+# *.c files rely on <linux/export.h> being included indirectly.
+check_unnecessary_include_linux_export_h () {
+
+ git -C "${srctree:-.}" grep --files-with-matches '#include[[:space:]]*<linux/export\.h>' \
+ -- '*.[c]' :^tools/ |
+ xargs git -C "${srctree:-.}" grep --files-without-match -E 'EXPORT_SYMBOL((_NS)?(_GPL)?|_GPL_FOR_MODULES)\(.*\)' |
+ xargs printf "%s: warning: EXPORT_SYMBOL() is not used, but #include <linux/export.h> is present\n" >&2
+}
+
check_tracked_ignored_files
check_missing_include_linux_export_h
+check_unnecessary_include_linux_export_h
--
2.43.0
next prev parent reply other threads:[~2025-06-01 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 13:31 [PATCH v2 1/4] kbuild: move W=1 check for scripts/misc-check to top-level Makefile Masahiro Yamada
2025-06-01 13:31 ` [PATCH v2 2/4] scripts/misc-check: add double-quotes to satisfy shellcheck Masahiro Yamada
2025-06-01 13:31 ` [PATCH v2 3/4] scripts/misc-check: check missing #include <linux/export.h> when W=1 Masahiro Yamada
2025-06-04 4:52 ` Masahiro Yamada
2025-06-19 16:01 ` Jakub Kicinski
2025-06-19 16:13 ` Masahiro Yamada
2025-06-19 16:26 ` Jakub Kicinski
2025-06-01 13:31 ` Masahiro Yamada [this message]
2025-06-02 22:06 ` [PATCH v2 1/4] kbuild: move W=1 check for scripts/misc-check to top-level Makefile Nathan Chancellor
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=20250601133230.4085512-4-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®