From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [linux-rt-devel:linux-5.13.y-rt-testing 223/226] kernel/locking/rtmutex_api.c:501: warning: expecting prototype for rwsem_rt_mutex_try_lock(). Prototype was for rwsem_rt_mutex_trylock() instead
Date: Sat, 10 Jul 2021 11:55:35 +0800 [thread overview]
Message-ID: <202107101129.VguCw1H0-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3487 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.13.y-rt-testing
head: db8ae8e3fd71ddc8103a71d002780bed20e5d9de
commit: 8babe6924dddf3c0e3ac5390630c4905c7ea7c73 [223/226] locking/rt: Fix kernel doc for rwsem_rt_mutex_try_lock()
config: alpha-randconfig-p001-20210709 (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/commit/?id=8babe6924dddf3c0e3ac5390630c4905c7ea7c73
git remote add linux-rt-devel https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git
git fetch --no-tags linux-rt-devel linux-5.13.y-rt-testing
git checkout 8babe6924dddf3c0e3ac5390630c4905c7ea7c73
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross O=build_dir ARCH=alpha SHELL=/bin/bash kernel/locking/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/locking/rtmutex_api.c:501: warning: expecting prototype for rwsem_rt_mutex_try_lock(). Prototype was for rwsem_rt_mutex_trylock() instead
vim +501 kernel/locking/rtmutex_api.c
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 491
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 492 /**
8babe6924dddf3c0 Thomas Gleixner 2021-07-09 493 * rwsem_rt_mutex_try_lock - Try to lock a rt_mutex
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 494 * @lock: The rt_mutex to be locked
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 495 *
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 496 * The function does no lockdep operations on @lock. The lockdep state
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 497 * changes have to be done on the callsite related to the locking primitive
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 498 * which embeds the rtmutex. Otherwise lockdep has double tracking.
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 499 */
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 500 int __sched rwsem_rt_mutex_trylock(struct rt_mutex *lock)
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 @501 {
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 502 if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEXES) &&
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 503 WARN_ON_ONCE(in_nmi() | in_hardirq()))
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 504 return 0;
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 505
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 506 if (likely(rt_mutex_cmpxchg_acquire(lock, NULL, current)))
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 507 return 1;
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 508
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 509 return rt_mutex_slowtrylock(lock);
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 510 }
e03cbdcf154eddbc Thomas Gleixner 2021-07-06 511
:::::: The code at line 501 was first introduced by commit
:::::: e03cbdcf154eddbc014705b6e2ebacd755d6ab39 locking/rtmutex: Provide lockdep less variants of rtmutex interfaces
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 22821 bytes --]
next reply other threads:[~2021-07-10 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 3:55 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-10 2:21 [linux-rt-devel:linux-5.13.y-rt-testing 223/226] kernel/locking/rtmutex_api.c:501: warning: expecting prototype for rwsem_rt_mutex_try_lock(). Prototype was for rwsem_rt_mutex_trylock() instead 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=202107101129.VguCw1H0-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).