From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>,
arnd@arndb.de, mcgrof@kernel.org, petr.pavlu@suse.com,
da.gomez@kernel.org, samitolvanen@google.com,
peterz@infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
mhiramat@kernel.org, atomlin@atomlin.com, neelx@suse.com,
da.anzani@gmail.com, sean@ashe.io, chjohnst@mail.com,
steve@abita.co, mproche@mail.com, nick.lane@mail.com,
linux-arch@vger.kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] module: Extend module_blacklist parameter to built-in modules
Date: Thu, 6 Aug 2026 10:15:24 +0800 [thread overview]
Message-ID: <202608060957.II0PSh3B-lkp@intel.com> (raw)
In-Reply-To: <20260622140259.2974-1-atomlin@atomlin.com>
Hi Aaron,
kernel test robot noticed the following build errors:
[auto build test ERROR on soc/for-next]
[also build test ERROR on linus/master arnd-asm-generic/master v7.2-rc6 next-20260805]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Aaron-Tomlin/module-Extend-module_blacklist-parameter-to-built-in-modules/20260805-123559
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
patch link: https://lore.kernel.org/r/20260622140259.2974-1-atomlin%40atomlin.com
patch subject: [PATCH v2] module: Extend module_blacklist parameter to built-in modules
config: powerpc64-randconfig-002-20260806 (https://download.01.org/0day-ci/archive/20260806/202608060957.II0PSh3B-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260806/202608060957.II0PSh3B-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608060957.II0PSh3B-lkp@intel.com/
All errors (new ones prefixed by >>):
>> init/main.c:1364:17: error: call to undeclared function 'module_is_blacklisted'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1364 | if (modname && module_is_blacklisted(modname)) {
| ^
1 error generated.
vim +/module_is_blacklisted +1364 init/main.c
1355
1356 int __init_or_module do_one_initcall(initcall_t fn)
1357 {
1358 int count = preempt_count();
1359 char msgbuf[64];
1360 const char *modname;
1361 int ret;
1362
1363 modname = initcall_get_modname(fn);
> 1364 if (modname && module_is_blacklisted(modname)) {
1365 pr_info("Skipping initcall for blacklisted built-in module %s\n",
1366 modname);
1367 return 0;
1368 }
1369
1370 if (initcall_blacklisted(fn))
1371 return -EPERM;
1372
1373 do_trace_initcall_start(fn);
1374 ret = fn();
1375 do_trace_initcall_finish(fn, ret);
1376
1377 msgbuf[0] = 0;
1378
1379 if (preempt_count() != count) {
1380 sprintf(msgbuf, "preemption imbalance ");
1381 preempt_count_set(count);
1382 }
1383 if (irqs_disabled()) {
1384 strlcat(msgbuf, "disabled interrupts ", sizeof(msgbuf));
1385 local_irq_enable();
1386 }
1387 WARN(msgbuf[0], "initcall %pS returned with %s\n", fn, msgbuf);
1388
1389 add_latent_entropy();
1390 return ret;
1391 }
1392
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-06 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260622140259.2974-1-atomlin@atomlin.com>
2026-08-05 14:17 ` [PATCH v2] module: Extend module_blacklist parameter to built-in modules kernel test robot
2026-08-06 2:15 ` kernel test robot [this message]
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=202608060957.II0PSh3B-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=atomlin@atomlin.com \
--cc=chjohnst@mail.com \
--cc=da.anzani@gmail.com \
--cc=da.gomez@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mproche@mail.com \
--cc=neelx@suse.com \
--cc=nick.lane@mail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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