From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [peterz-queue:locking/core 25/27] kernel/locking/mutex.c:59:15: error: use of undeclared identifier 'lock'
Date: Sat, 07 Mar 2026 10:16:58 +0800 [thread overview]
Message-ID: <202603071012.LwOWygMP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
head: 6f3cd442fa6c0cfc46a20c0138fb131daaa99d2d
commit: 788b5792cd7586750f96c7fe4bc8859e6f5314e7 [25/27] locking/mutex: Add context analysis
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20260307/202603071012.LwOWygMP-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project c32caeec8158d634bb71ab8911a6031248b9fc47)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260307/202603071012.LwOWygMP-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/202603071012.LwOWygMP-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/locking/mutex.c:59:15: error: use of undeclared identifier 'lock'
59 | __must_hold(&lock->wait_lock)
| ^~~~
1 error generated.
vim +/lock +59 kernel/locking/mutex.c
57
58 static inline struct task_struct *__owner_task(unsigned long owner)
> 59 __must_hold(&lock->wait_lock)
60 {
61 return (struct task_struct *)(owner & ~MUTEX_FLAGS);
62 }
63
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-07 2:17 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=202603071012.LwOWygMP-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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