[PATCH v2 18/29] modpost: show warning if vmlinux is not found when processing modules

From: Masahiro Yamada
Date: Sun May 24 2020 - 11:44:06 EST


check_exports() does not print warnings about unresolved symbols if
vmlinux is missing because there would be too many.

This situation happens when you do 'make modules' from the clean
tree, or compile external modules against a kernel tree that has
not been completely built.

Not checking unresolved symbols is dangerous because you might be
building useless modules. At least it should be noted.

Signed-off-by: Masahiro Yamada <masahiroy@xxxxxxxxxx>
---

Changes in v2: None

scripts/mod/modpost.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 0a24d2c501c1..638c45d35292 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -2014,8 +2014,6 @@ static void read_symbols(const char *modname)

mod = new_module(modname);

- /* When there's no vmlinux, don't print warnings about
- * unresolved symbols (since there'll be too many ;) */
if (is_vmlinux(modname)) {
have_vmlinux = 1;
mod->skip = 1;
@@ -2627,6 +2625,13 @@ int main(int argc, char **argv)
if (files_source)
read_symbols_from_files(files_source);

+ /*
+ * When there's no vmlinux, don't print warnings about
+ * unresolved symbols (since there'll be too many ;)
+ */
+ if (!have_vmlinux)
+ warn("Symbol info of vmlinux is missing. Unresolved symbol check will be entirely skipped.\n");
+
err = 0;

for (mod = modules; mod; mod = mod->next) {
--
2.25.1