From: kernel test robot <lkp@intel.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jfern:nova/mm 6/31] error[E0133]: access to union field is unsafe and requires unsafe block
Date: Sat, 21 Feb 2026 01:13:35 +0800 [thread overview]
Message-ID: <202602210130.86eZe0Gi-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git nova/mm
head: d44aeb89db2e47449220a4721f5e89202bd7b128
commit: 6e05d1c7b5efa36e6e1c8581e1645c00eb6ab0f9 [6/31] rust: gpu: Add GPU buddy allocator bindings
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260221/202602210130.86eZe0Gi-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/20260221/202602210130.86eZe0Gi-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/202602210130.86eZe0Gi-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0133]: access to union field is unsafe and requires unsafe block
--> rust/kernel/ffi/clist.rs:331:28
|
331 | |p| &raw const (*p).$($field).+;
| ^^^^^^^^^^^^^ access to union field
|
::: rust/kernel/gpu/buddy.rs:433:21
|
433 | let clist = clist_create!(unsafe {
| _____________________-
434 | | self.list.as_raw(),
435 | | Block,
436 | | bindings::gpu_buddy_block,
437 | | __bindgen_anon_1.link
438 | | });
| |__________- in this macro invocation
|
= note: the field may not be properly initialized: using uninitialized data will cause undefined behavior
= note: this error originates in the macro `clist_create` (in Nightly builds, run with -Z macro-backtrace for more info)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-20 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202602210130.86eZe0Gi-lkp@intel.com \
--to=lkp@intel.com \
--cc=joelagnelf@nvidia.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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