From: kernel test robot <lkp@intel.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/2] locking: add mutex_lock_nospin()
Date: Sat, 7 Mar 2026 02:24:18 +0800 [thread overview]
Message-ID: <202603070229.G9hHE2az-lkp@intel.com> (raw)
In-Reply-To: <20260304074650.58165-2-laoar.shao@gmail.com>
Hi Yafang,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on linus/master v7.0-rc2 next-20260305]
[cannot apply to trace/for-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/Yafang-Shao/locking-add-mutex_lock_nospin/20260304-155633
base: tip/locking/core
patch link: https://lore.kernel.org/r/20260304074650.58165-2-laoar.shao%40gmail.com
patch subject: [RFC PATCH 1/2] locking: add mutex_lock_nospin()
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20260307/202603070229.G9hHE2az-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260307/202603070229.G9hHE2az-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/202603070229.G9hHE2az-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
kernel/locking/mutex.c: In function 'mutex_lock_nospin':
>> kernel/locking/mutex.c:299:17: error: implicit declaration of function '__mutex_lock_nospin'; did you mean 'mutex_lock_nospin'? [-Wimplicit-function-declaration]
299 | __mutex_lock_nospin(lock);
| ^~~~~~~~~~~~~~~~~~~
| mutex_lock_nospin
kernel/locking/mutex.c: In function '__mutex_lock_common':
>> kernel/locking/mutex.c:630:13: error: too many arguments to function 'mutex_optimistic_spin'; expected 3, have 4
630 | mutex_optimistic_spin(lock, ww_ctx, NULL, nospin)) {
| ^~~~~~~~~~~~~~~~~~~~~ ~~~~~~
kernel/locking/mutex.c:532:1: note: declared here
532 | mutex_optimistic_spin(struct mutex *lock, struct ww_acquire_ctx *ww_ctx,
| ^~~~~~~~~~~~~~~~~~~~~
kernel/locking/mutex.c:731:29: error: too many arguments to function 'mutex_optimistic_spin'; expected 3, have 4
731 | if (mutex_optimistic_spin(lock, ww_ctx, &waiter, nospin))
| ^~~~~~~~~~~~~~~~~~~~~ ~~~~~~
kernel/locking/mutex.c:532:1: note: declared here
532 | mutex_optimistic_spin(struct mutex *lock, struct ww_acquire_ctx *ww_ctx,
| ^~~~~~~~~~~~~~~~~~~~~
kernel/locking/mutex.c: At top level:
>> kernel/locking/mutex.c:792:1: error: static declaration of '__mutex_lock_nospin' follows non-static declaration
792 | __mutex_lock_nospin(struct mutex *lock, unsigned int state, unsigned int subclass,
| ^~~~~~~~~~~~~~~~~~~
kernel/locking/mutex.c:299:17: note: previous implicit declaration of '__mutex_lock_nospin' with type 'int()'
299 | __mutex_lock_nospin(lock);
| ^~~~~~~~~~~~~~~~~~~
>> kernel/locking/mutex.c:792:1: warning: '__mutex_lock_nospin' defined but not used [-Wunused-function]
792 | __mutex_lock_nospin(struct mutex *lock, unsigned int state, unsigned int subclass,
| ^~~~~~~~~~~~~~~~~~~
vim +299 kernel/locking/mutex.c
293
294 void __sched mutex_lock_nospin(struct mutex *lock)
295 {
296 might_sleep();
297
298 if (!__mutex_trylock_fast(lock))
> 299 __mutex_lock_nospin(lock);
300 }
301 #endif
302
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-06 18:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 7:46 [RFC PATCH 0/2] disable optimistic spinning for ftrace_lock Yafang Shao
2026-03-04 7:46 ` [RFC PATCH 1/2] locking: add mutex_lock_nospin() Yafang Shao
2026-03-04 9:02 ` Peter Zijlstra
2026-03-04 9:37 ` Yafang Shao
2026-03-04 10:11 ` Peter Zijlstra
2026-03-04 11:52 ` Yafang Shao
2026-03-04 12:41 ` Peter Zijlstra
2026-03-04 14:25 ` Yafang Shao
2026-03-04 9:54 ` David Laight
2026-03-04 20:57 ` Steven Rostedt
2026-03-04 21:44 ` David Laight
2026-03-05 2:17 ` Yafang Shao
2026-03-05 2:28 ` Steven Rostedt
2026-03-05 2:33 ` Yafang Shao
2026-03-05 3:00 ` Steven Rostedt
2026-03-05 3:08 ` Yafang Shao
2026-03-05 4:30 ` Waiman Long
2026-03-05 5:40 ` Yafang Shao
2026-03-05 13:21 ` Steven Rostedt
2026-03-06 2:22 ` Yafang Shao
2026-03-06 10:00 ` David Laight
2026-03-09 2:34 ` Yafang Shao
2026-03-05 18:34 ` Waiman Long
2026-03-05 18:44 ` Waiman Long
2026-03-06 2:27 ` Yafang Shao
2026-03-05 9:32 ` David Laight
2026-03-05 19:00 ` Waiman Long
2026-03-06 2:33 ` Yafang Shao
2026-03-06 18:12 ` kernel test robot
2026-03-06 18:24 ` kernel test robot [this message]
2026-03-04 7:46 ` [RFC PATCH 2/2] ftrace: disable optimistic spinning for ftrace_lock Yafang Shao
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=202603070229.G9hHE2az-lkp@intel.com \
--to=lkp@intel.com \
--cc=laoar.shao@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.