From: kernel test robot <lkp@intel.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
Date: Fri, 21 Nov 2025 04:32:22 +0800 [thread overview]
Message-ID: <202511210427.s8clI0Az-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fd95357fd8c6778ac7dea6c57a19b8b182b6e91f
commit: 584e61452f75bfeac2cdd83730b4059526ec60c7 rust: helpers: Remove volatile qualifier from io helpers
date: 7 months ago
config: um-randconfig-001-20251121 (https://download.01.org/0day-ci/archive/20251121/202511210427.s8clI0Az-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9e9fe08b16ea2c4d9867fb4974edf2a3776d6ece)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251121/202511210427.s8clI0Az-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/202511210427.s8clI0Az-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
--> rust/kernel/block/mq/operations.rs:15:33
|
15 | use core::{marker::PhantomData, sync::atomic::AtomicU64, sync::atomic::Ordering};
| ^^^^^^^^^^^^^^---------
| | |
| | help: a similar name exists in the module: `AtomicU32`
| no `AtomicU64` in `sync::atomic`
--
>> error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
--> rust/kernel/block/mq/request.rs:16:20
|
16 | sync::atomic::{AtomicU64, Ordering},
| ^^^^^^^^^
| |
| no `AtomicU64` in `sync::atomic`
| help: a similar name exists in the module: `AtomicU32`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `timeout`
--> rust/kernel/block/mq/tag_set.rs:50:21
|
50 | timeout: 0, // 0 means default which is 30Hz in C
| ^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `numa_node`
--> rust/kernel/block/mq/tag_set.rs:51:21
|
51 | numa_node: bindings::NUMA_NO_NODE,
| ^^^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `queue_depth`
--> rust/kernel/block/mq/tag_set.rs:52:21
|
52 | queue_depth: num_tags,
| ^^^^^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `cmd_size`
--> rust/kernel/block/mq/tag_set.rs:53:21
|
53 | cmd_size,
| ^^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `flags`
--> rust/kernel/block/mq/tag_set.rs:54:21
|
54 | flags: 0,
| ^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `driver_data`
--> rust/kernel/block/mq/tag_set.rs:55:21
|
55 | driver_data: core::ptr::null_mut::<crate::ffi::c_void>(),
| ^^^^^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `blk_mq_tag_set` has no field named `nr_maps`
--> rust/kernel/block/mq/tag_set.rs:56:21
|
56 | nr_maps: num_maps,
| ^^^^^^^ `blk_mq_tag_set` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `block_device_operations` has no field named `submit_bio`
--> rust/kernel/block/mq/gen_disk.rs:116:13
|
116 | submit_bio: None,
| ^^^^^^^^^^ `block_device_operations` does not have this field
|
= note: available fields are: `_address`
--
>> error[E0560]: struct `block_device_operations` has no field named `open`
--> rust/kernel/block/mq/gen_disk.rs:117:13
|
117 | open: None,
| ^^^^ `block_device_operations` does not have this field
|
= note: available fields are: `_address`
..
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-20 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 20:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-27 7:06 error[E0432]: unresolved import `core::sync::atomic::AtomicU64` 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=202511210427.s8clI0Az-lkp@intel.com \
--to=lkp@intel.com \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).