From: kernel test robot <lkp@intel.com>
To: "Ritvik Gupta" <ritvikfoss@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
skhan@linuxfoundation.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v3] rust: kernel: introduce `unsafe_precondition_assert!` macro
Date: Tue, 5 Aug 2025 08:17:51 +0800 [thread overview]
Message-ID: <202508050756.oFg4cjPu-lkp@intel.com> (raw)
In-Reply-To: <20250731111234.28602-1-ritvikfoss@gmail.com>
Hi Ritvik,
kernel test robot noticed the following build errors:
[auto build test ERROR on dff64b072708ffef23c117fa1ee1ea59eb417807]
url: https://github.com/intel-lab-lkp/linux/commits/Ritvik-Gupta/rust-kernel-introduce-unsafe_precondition_assert-macro/20250731-191444
base: dff64b072708ffef23c117fa1ee1ea59eb417807
patch link: https://lore.kernel.org/r/20250731111234.28602-1-ritvikfoss%40gmail.com
patch subject: [PATCH v3] rust: kernel: introduce `unsafe_precondition_assert!` macro
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250805/202508050756.oFg4cjPu-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/20250805/202508050756.oFg4cjPu-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/202508050756.oFg4cjPu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: cannot find macro `unsafe_precondition_assert` in this scope
--> rust/doctests_kernel_generated.rs:8012:5
|
8012 | unsafe_precondition_assert!(!buf.is_null(), "buf must not be null");
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
::: /opt/cross/rustc-1.88.0-bindgen-0.72.0/rustup/toolchains/1.88.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ub_checks.rs:52:1
|
52 | macro_rules! assert_unsafe_precondition {
| --------------------------------------- similarly named macro `assert_unsafe_precondition` defined here
|
help: a macro with a similar name exists
|
8012 - unsafe_precondition_assert!(!buf.is_null(), "buf must not be null");
8012 + assert_unsafe_precondition!(!buf.is_null(), "buf must not be null");
|
help: consider importing this macro
|
3 + use kernel::unsafe_precondition_assert;
|
--
>> error: cannot find macro `unsafe_precondition_assert` in this scope
--> rust/doctests_kernel_generated.rs:8013:5
|
8013 | unsafe_precondition_assert!((buf as usize) % 16 == 0, "buf must be 16-byte aligned");
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
::: /opt/cross/rustc-1.88.0-bindgen-0.72.0/rustup/toolchains/1.88.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ub_checks.rs:52:1
|
52 | macro_rules! assert_unsafe_precondition {
| --------------------------------------- similarly named macro `assert_unsafe_precondition` defined here
|
help: a macro with a similar name exists
|
8013 - unsafe_precondition_assert!((buf as usize) % 16 == 0, "buf must be 16-byte aligned");
8013 + assert_unsafe_precondition!((buf as usize) % 16 == 0, "buf must be 16-byte aligned");
|
help: consider importing this macro
|
3 + use kernel::unsafe_precondition_assert;
|
--
>> error: cannot find macro `unsafe_precondition_assert` in this scope
--> rust/doctests_kernel_generated.rs:8014:5
|
8014 | unsafe_precondition_assert!(
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
::: /opt/cross/rustc-1.88.0-bindgen-0.72.0/rustup/toolchains/1.88.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ub_checks.rs:52:1
|
52 | macro_rules! assert_unsafe_precondition {
| --------------------------------------- similarly named macro `assert_unsafe_precondition` defined here
|
help: a macro with a similar name exists
|
8014 - unsafe_precondition_assert!(
8014 + assert_unsafe_precondition!(
|
help: consider importing this macro
|
3 + use kernel::unsafe_precondition_assert;
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-05 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 11:12 [PATCH v3] rust: kernel: introduce `unsafe_precondition_assert!` macro Ritvik Gupta
2025-07-31 11:42 ` Miguel Ojeda
2025-08-01 13:49 ` Ritvik Gupta
2025-08-05 0:17 ` 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=202508050756.oFg4cjPu-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=ritvikfoss@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tmgross@umich.edu \
/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.