From: kernel test robot <lkp@intel.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 1/5] locking/mutex: implement mutex_trylock_nested
Date: Wed, 7 May 2025 15:31:15 +0800 [thread overview]
Message-ID: <202505071523.2k7QnWJd-lkp@intel.com> (raw)
In-Reply-To: <20250430203013.366479-2-mlevitsk@redhat.com>
Hi Maxim,
kernel test robot noticed the following build errors:
[auto build test ERROR on kvmarm/next]
[also build test ERROR on kvm/queue kvm/next tip/locking/core linus/master v6.15-rc5 next-20250506]
[cannot apply to kvm/linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Maxim-Levitsky/locking-mutex-implement-mutex_trylock_nested/20250501-043418
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next
patch link: https://lore.kernel.org/r/20250430203013.366479-2-mlevitsk%40redhat.com
patch subject: [PATCH v4 1/5] locking/mutex: implement mutex_trylock_nested
config: x86_64-randconfig-072-20250501 (https://download.01.org/0day-ci/archive/20250507/202505071523.2k7QnWJd-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071523.2k7QnWJd-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/202505071523.2k7QnWJd-lkp@intel.com/
All errors (new ones prefixed by >>):
***
*** Rust bindings generator 'bindgen' < 0.69.5 together with libclang >= 19.1
*** may not work due to a bug (https://github.com/rust-lang/rust-bindgen/pull/2824),
*** unless patched (like Debian's).
*** Your bindgen version: 0.65.1
*** Your libclang version: 20.1.2
***
***
*** Please see Documentation/rust/quick-start.rst for details
*** on how to set up the Rust support.
***
>> error[E0425]: cannot find function `mutex_trylock` in crate `bindings`
--> rust/kernel/sync/lock/mutex.rs:129:41
|
129 | let result = unsafe { bindings::mutex_trylock(ptr) };
| ^^^^^^^^^^^^^ help: a function with a similar name exists: `mutex_lock`
|
::: rust/bindings/bindings_helpers_generated.rs:181:5
|
181 | pub fn mutex_lock(lock: *mut mutex);
| ----------------------------------- similarly named function `mutex_lock` defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-05-07 7:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250430203013.366479-2-mlevitsk@redhat.com>]
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=202505071523.2k7QnWJd-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mlevitsk@redhat.com \
--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