From: kernel test robot <lkp@intel.com>
To: Alice Ryhl <aliceryhl@google.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH v3] rust: add global lock support
Date: Wed, 11 Sep 2024 22:10:30 +0800 [thread overview]
Message-ID: <202409112144.dcfxjqII-lkp@intel.com> (raw)
In-Reply-To: <20240910-static-mutex-v3-1-5bebd11bdf3b@google.com>
Hi Alice,
kernel test robot noticed the following build errors:
[auto build test ERROR on 93dc3be19450447a3a7090bd1dfb9f3daac3e8d2]
url: https://github.com/intel-lab-lkp/linux/commits/Alice-Ryhl/rust-add-global-lock-support/20240910-222519
base: 93dc3be19450447a3a7090bd1dfb9f3daac3e8d2
patch link: https://lore.kernel.org/r/20240910-static-mutex-v3-1-5bebd11bdf3b%40google.com
patch subject: [PATCH v3] rust: add global lock support
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240911/202409112144.dcfxjqII-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240911/202409112144.dcfxjqII-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/202409112144.dcfxjqII-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0432]: unresolved import `super::__static_lock_ty_MY_COUNTER`
--> rust/doctests_kernel_generated.rs:4818:1
|
4818 | / kernel::sync::global_lock! {
4819 | | // SAFETY: Initialized in module initializer before first use.
4820 | | static MY_COUNTER: Mutex<u32> = unsafe { uninit };
4821 | | value: 0;
4822 | | }
| |_^ no `__static_lock_ty_MY_COUNTER` in the root
|
= note: this error originates in the macro `$crate::global_lock` which comes from the expansion of the macro `kernel::sync::global_lock` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0432]: unresolved import `super::__static_lock_ty_MY_MUTEX`
--> rust/doctests_kernel_generated.rs:4886:1
|
4886 | / kernel::sync::global_lock! {
4887 | | // SAFETY: Initialized in module initializer before first use.
4888 | | static MY_MUTEX: Mutex<()> = unsafe { uninit };
4889 | | value: ();
4890 | | guard: MyGuard;
4891 | | locked_by: LockedByMyMutex;
4892 | | }
| |_^ no `__static_lock_ty_MY_MUTEX` in the root
|
= note: this error originates in the macro `$crate::global_lock` which comes from the expansion of the macro `kernel::sync::global_lock` (in Nightly builds, run with -Z macro-backtrace for more info)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-11 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 14:23 [PATCH v3] rust: add global lock support Alice Ryhl
2024-09-11 14:10 ` kernel test robot [this message]
2024-09-13 16:01 ` Simona Vetter
2024-09-13 16:10 ` Alice Ryhl
2024-09-13 16:52 ` Benno Lossin
2024-09-16 15:09 ` Simona Vetter
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=202409112144.dcfxjqII-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@samsung.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.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).