All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jamie Lindsey <jamie@matrixforgelabs.com>,
	rust-for-linux@vger.kernel.org,
	linux-security-module@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	ojeda@kernel.org, paul@paul-moore.com, aliceryhl@google.com,
	jmorris@namei.org, serge@hallyn.com, jamie@matrixforgelabs.com
Subject: Re: [PATCH v2 3/5] rust: kernel: add LSM abstraction layer
Date: Thu, 12 Mar 2026 06:58:50 +0800	[thread overview]
Message-ID: <202603120654.DWidINbR-lkp@intel.com> (raw)
In-Reply-To: <0102019cdb4c705e-7d46b4f3-5cbb-4a6a-b315-e10f182fa987-000000@eu-west-1.amazonses.com>

Hi Jamie,

kernel test robot noticed the following build errors:

[auto build test ERROR on rust/rust-next]
[also build test ERROR on linus/master v7.0-rc3 next-20260311]
[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/Jamie-Lindsey/rust-helpers-add-C-shims-for-LSM-hook-initialisation/20260311-131258
base:   https://github.com/Rust-for-Linux/linux rust-next
patch link:    https://lore.kernel.org/r/0102019cdb4c705e-7d46b4f3-5cbb-4a6a-b315-e10f182fa987-000000%40eu-west-1.amazonses.com
patch subject: [PATCH v2 3/5] rust: kernel: add LSM abstraction layer
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260312/202603120654.DWidINbR-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260312/202603120654.DWidINbR-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/202603120654.DWidINbR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0433]: failed to resolve: use of unresolved module or unlinked crate `bindings`
   --> rust/doctests_kernel_generated.rs:8845:40
   |
   8845 | kernel::define_lsm!(MyLsm, "my_lsm\0", bindings::LSM_ID_UNDEF as u64);
   |                                        ^^^^^^^^ use of unresolved module or unlinked crate `bindings`
   |
   = help: you might be missing a crate named `bindings`
   = help: consider importing this crate:
   kernel::bindings
--
>> error[E0412]: cannot find type `MyLsm` in this scope
   --> rust/doctests_kernel_generated.rs:8845:21
   |
   8845 | kernel::define_lsm!(MyLsm, "my_lsm\0", bindings::LSM_ID_UNDEF as u64);
   |                     ^^^^^ not found in this scope
--
>> error[E0433]: failed to resolve: use of unresolved module or unlinked crate `bindings`
   --> rust/doctests_kernel_generated.rs:8898:44
   |
   8898 | kernel::define_lsm!(MyLsmType, "my_lsm\0", bindings::LSM_ID_UNDEF as u64);
   |                                            ^^^^^^^^ use of unresolved module or unlinked crate `bindings`
   |
   = help: you might be missing a crate named `bindings`
   = help: consider importing this crate:
   kernel::bindings
--
>> error[E0412]: cannot find type `MyLsmType` in this scope
   --> rust/doctests_kernel_generated.rs:8898:21
   |
   8898 | kernel::define_lsm!(MyLsmType, "my_lsm\0", bindings::LSM_ID_UNDEF as u64);
   |                     ^^^^^^^^^ not found in this scope

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

  parent reply	other threads:[~2026-03-11 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260311050854.657422-1-jamie@matrixforgelabs.com>
2026-03-11  5:09 ` [PATCH v2 1/5] rust: bindings: include lsm_hooks.h to expose LSM types to bindgen Jamie Lindsey
2026-03-11  5:09 ` [PATCH v2 2/5] rust: helpers: add C shims for LSM hook initialisation Jamie Lindsey
2026-03-11 23:13   ` kernel test robot
2026-03-11  5:09 ` [PATCH v2 3/5] rust: kernel: add LSM abstraction layer Jamie Lindsey
2026-03-11  6:49   ` Miguel Ojeda
2026-03-11 12:07   ` kernel test robot
2026-03-11 22:58   ` kernel test robot [this message]
2026-03-11  5:09 ` [PATCH v2 4/5] security: add Rust LSM sample (CONFIG_SECURITY_RUST_LSM) Jamie Lindsey
2026-03-11  5:09 ` [PATCH v2 5/5] Documentation: rust: add LSM abstraction guide; update MAINTAINERS Jamie Lindsey

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=202603120654.DWidINbR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aliceryhl@google.com \
    --cc=jamie@matrixforgelabs.com \
    --cc=jmorris@namei.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=serge@hallyn.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.