Linux Modules
 help / color / mirror / Atom feed
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, ojeda@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	akpm@linux-foundation.org, mhiramat@kernel.org, boqun@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, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 2/2] module: Rename module_blacklist to module_denylist
Date: Wed, 9 Sep 2026 03:35:01 +0200	[thread overview]
Message-ID: <202609090311.bhj7AUr7-lkp@intel.com> (raw)
In-Reply-To: <20260903185557.183224-3-atomlin@atomlin.com>

Hi Aaron,

kernel test robot noticed the following build errors:

[auto build test ERROR on rust/rust-next]
[also build test ERROR on soc/for-next linus/master v7.3-rc2 next-20260908]
[cannot apply to arnd-asm-generic/master]
[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/20260903-145556
base:   https://github.com/Rust-for-Linux/linux rust-next
patch link:    https://lore.kernel.org/r/20260903185557.183224-3-atomlin%40atomlin.com
patch subject: [PATCH v10 2/2] module: Rename module_blacklist to module_denylist
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260909/202609090311.bhj7AUr7-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260909/202609090311.bhj7AUr7-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/202609090311.bhj7AUr7-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> rust/doctests_kernel_generated.rs:7459:1
   |
   7459 | / module! {
   7460 | |    type: MyModule,
   7461 | |    name: "module_firmware_test",
   7462 | |    authors: ["Rust for Linux"],
   7463 | |    description: "module_firmware! test module",
   7464 | |    license: "GPL",
   7465 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
   --> rust/doctests_kernel_generated.rs:7459:1
   |
   7459 | / module! {
   7460 | |    type: MyModule,
   7461 | |    name: "module_firmware_test",
   7462 | |    authors: ["Rust for Linux"],
   7463 | |    description: "module_firmware! test module",
   7464 | |    license: "GPL",
   7465 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> rust/doctests_kernel_generated.rs:12739:1
   |
   12739 | / kernel::module_phy_driver! {
   12740 | |     drivers: [PhySample],
   12741 | |     device_table: [
   12742 | |         DeviceId::new_with_driver::<PhySample>()
   ...     |
   12747 | |     license: "GPL",
   12748 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_phy_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
   --> rust/doctests_kernel_generated.rs:12739:1
   |
   12739 | / kernel::module_phy_driver! {
   12740 | |     drivers: [PhySample],
   12741 | |     device_table: [
   12742 | |         DeviceId::new_with_driver::<PhySample>()
   ...     |
   12747 | |     license: "GPL",
   12748 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_phy_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_minimal.rs:7:1
   |
   7 | / module! {
   8 | |     type: RustMinimal,
   9 | |     name: "rust_minimal",
   10 | |     authors: ["Rust for Linux Contributors"],
   ...  |
   22 | |     },
   23 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_minimal.rs:7:1
   |
   7 | / module! {
   8 | |     type: RustMinimal,
   9 | |     name: "rust_minimal",
   10 | |     authors: ["Rust for Linux Contributors"],
   ...  |
   22 | |     },
   23 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_misc_device.rs:136:1
   |
   136 | / module! {
   137 | |     type: RustMiscDeviceModule,
   138 | |     name: "rust_misc_device",
   139 | |     authors: ["Lee Jones"],
   140 | |     description: "Rust misc device sample",
   141 | |     license: "GPL",
   142 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_misc_device.rs:136:1
   |
   136 | / module! {
   137 | |     type: RustMiscDeviceModule,
   138 | |     name: "rust_misc_device",
   139 | |     authors: ["Lee Jones"],
   140 | |     description: "Rust misc device sample",
   141 | |     license: "GPL",
   142 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_print_main.rs:8:1
   |
   8 | / module! {
   9 | |     type: RustPrint,
   10 | |     name: "rust_print",
   11 | |     authors: ["Rust for Linux Contributors"],
   12 | |     description: "Rust printing macros sample",
   13 | |     license: "GPL",
   14 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_print_main.rs:8:1
   |
   8 | / module! {
   9 | |     type: RustPrint,
   10 | |     name: "rust_print",
   11 | |     authors: ["Rust for Linux Contributors"],
   12 | |     description: "Rust printing macros sample",
   13 | |     license: "GPL",
   14 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
   --> samples/rust/rust_debugfs.rs:58:1
   |
   58 | / kernel::module_platform_driver! {
   59 | |     type: RustDebugFs,
   60 | |     name: "rust_debugfs",
   61 | |     authors: ["Matthew Maurer"],
   62 | |     description: "Rust DebugFS usage sample",
   63 | |     license: "GPL",
   64 | | }
   | |_^ not found in `::kernel::bindings`
   |
   = note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_platform_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
..

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-09-09  1:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 18:55 [PATCH v10 0/2] module: Extend module_blacklist parameter to built-in modules Aaron Tomlin
2026-09-03 18:55 ` [PATCH v10 1/2] " Aaron Tomlin
2026-09-03 19:13   ` sashiko-bot
2026-09-04 14:34     ` Aaron Tomlin
2026-09-06 13:39       ` Gary Guo
2026-09-06 15:07         ` Aaron Tomlin
2026-09-03 20:23   ` Aaron Tomlin
2026-09-03 18:55 ` [PATCH v10 2/2] module: Rename module_blacklist to module_denylist Aaron Tomlin
2026-09-03 19:07   ` sashiko-bot
2026-09-04 15:13     ` Aaron Tomlin
2026-09-09  1:35   ` kernel test robot [this message]
2026-09-03 20:29 ` [PATCH v10 0/2] module: Extend module_blacklist parameter to built-in modules Andrew Morton
2026-09-04 14:59   ` Aaron Tomlin
2026-09-06  0:28     ` Andrew Morton
2026-09-06  9:56       ` Arnd Bergmann
2026-09-06 12:33         ` Gary Guo
2026-09-06 14:08         ` Aaron Tomlin
2026-09-09 13:22           ` Alice Ryhl
2026-09-06 13:15       ` Aaron Tomlin

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=202609090311.bhj7AUr7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=atomlin@atomlin.com \
    --cc=boqun@kernel.org \
    --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=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=petr.pavlu@suse.com \
    --cc=rust-for-linux@vger.kernel.org \
    --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