From: kernel test robot <lkp@intel.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Danilo Krummrich <dakr@kernel.org>, Gary Guo <gary@garyguo.net>,
Alice Ryhl <aliceryhl@google.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Alistair Popple <apopple@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
John Hubbard <jhubbard@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
Timur Tabi <ttabi@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
Eliot Courtney <ecourtney@nvidia.com>,
rust-for-linux@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH v3] gpu: nova-core: gsp: fix undefined behavior in command queue code
Date: Sat, 28 Mar 2026 04:03:38 +0800 [thread overview]
Message-ID: <202603280326.ucDKVaf2-lkp@intel.com> (raw)
In-Reply-To: <20260326-cmdq-ub-fix-v3-1-96af2148ca5c@nvidia.com>
Hi Alexandre,
kernel test robot noticed the following build errors:
[auto build test ERROR on dff8302ca1d0e773c90dbeeb05e759f995c95482]
url: https://github.com/intel-lab-lkp/linux/commits/Alexandre-Courbot/gpu-nova-core-gsp-fix-undefined-behavior-in-command-queue-code/20260327-003216
base: dff8302ca1d0e773c90dbeeb05e759f995c95482
patch link: https://lore.kernel.org/r/20260326-cmdq-ub-fix-v3-1-96af2148ca5c%40nvidia.com
patch subject: [PATCH v3] gpu: nova-core: gsp: fix undefined behavior in command queue code
config: um-randconfig-002-20260327 (https://download.01.org/0day-ci/archive/20260328/202603280326.ucDKVaf2-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 054e11d1a17e5ba88bb1a8ef32fad3346e80b186)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260328/202603280326.ucDKVaf2-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/202603280326.ucDKVaf2-lkp@intel.com/
All errors (new ones prefixed by >>):
/usr/bin/ld: warning: .tmp_vmlinux1 has a LOAD segment with RWX permissions
/usr/bin/ld: drivers/gpu/nova-core/nova_core.o: in function `<core::ops::range::Range<usize> as kernel::ptr::projection::ProjectIndex<[[u8; 4096]]>>::index::{closure#0}':
>> rust/kernel/build_assert.rs:28:(.text+0xfb16): undefined reference to `rust_build_error'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
vim +28 rust/kernel/build_assert.rs
614724e780f587 Miguel Ojeda 2024-11-23 7
0f595bab9d1c1a Gary Guo 2022-11-10 8 /// Fails the build if the code path calling `build_error!` can possibly be executed.
0f595bab9d1c1a Gary Guo 2022-11-10 9 ///
0f595bab9d1c1a Gary Guo 2022-11-10 10 /// If the macro is executed in const context, `build_error!` will panic.
0f595bab9d1c1a Gary Guo 2022-11-10 11 /// If the compiler or optimizer cannot guarantee that `build_error!` can never
0f595bab9d1c1a Gary Guo 2022-11-10 12 /// be called, a build error will be triggered.
0f595bab9d1c1a Gary Guo 2022-11-10 13 ///
0f595bab9d1c1a Gary Guo 2022-11-10 14 /// # Examples
0f595bab9d1c1a Gary Guo 2022-11-10 15 ///
0f595bab9d1c1a Gary Guo 2022-11-10 16 /// ```
0f595bab9d1c1a Gary Guo 2022-11-10 17 /// #[inline]
0f595bab9d1c1a Gary Guo 2022-11-10 18 /// fn foo(a: usize) -> usize {
0f595bab9d1c1a Gary Guo 2022-11-10 19 /// a.checked_add(1).unwrap_or_else(|| build_error!("overflow"))
0f595bab9d1c1a Gary Guo 2022-11-10 20 /// }
0f595bab9d1c1a Gary Guo 2022-11-10 21 ///
0f595bab9d1c1a Gary Guo 2022-11-10 22 /// assert_eq!(foo(usize::MAX - 1), usize::MAX); // OK.
0f595bab9d1c1a Gary Guo 2022-11-10 23 /// // foo(usize::MAX); // Fails to compile.
0f595bab9d1c1a Gary Guo 2022-11-10 24 /// ```
0f595bab9d1c1a Gary Guo 2022-11-10 25 #[macro_export]
0f595bab9d1c1a Gary Guo 2022-11-10 26 macro_rules! build_error {
0f595bab9d1c1a Gary Guo 2022-11-10 27 () => {{
614724e780f587 Miguel Ojeda 2024-11-23 @28 $crate::build_assert::build_error("")
0f595bab9d1c1a Gary Guo 2022-11-10 29 }};
0f595bab9d1c1a Gary Guo 2022-11-10 30 ($msg:expr) => {{
614724e780f587 Miguel Ojeda 2024-11-23 31 $crate::build_assert::build_error($msg)
0f595bab9d1c1a Gary Guo 2022-11-10 32 }};
0f595bab9d1c1a Gary Guo 2022-11-10 33 }
0f595bab9d1c1a Gary Guo 2022-11-10 34
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-27 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 5:43 [PATCH v3] gpu: nova-core: gsp: fix undefined behavior in command queue code Alexandre Courbot
2026-03-27 6:56 ` Alexandre Courbot
2026-03-27 12:23 ` Gary Guo
2026-03-27 14:34 ` Danilo Krummrich
2026-03-27 20:03 ` kernel test robot [this message]
2026-03-28 5:53 ` kernel test robot
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=202603280326.ucDKVaf2-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=zhiw@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox