From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-rt-devel:linux-5.13.y-rt-rebase 95/222] kernel/locking/rtmutex_api.c:491: warning: expecting prototype for rwsem_rt_mutex_try_lock_nolockdep(). Prototype was for rwsem_rt_mutex_trylock() instead
Date: Thu, 08 Jul 2021 20:53:18 +0800 [thread overview]
Message-ID: <202107082005.N22r0YHL-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2400 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.13.y-rt-rebase
head: 7e175e6b59975c8901ad370f7818937f68de45c1
commit: e03cbdcf154eddbc014705b6e2ebacd755d6ab39 [95/222] locking/rtmutex: Provide lockdep less variants of rtmutex interfaces
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-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=e03cbdcf154eddbc014705b6e2ebacd755d6ab39
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-rebase
git checkout e03cbdcf154eddbc014705b6e2ebacd755d6ab39
# 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=powerpc SHELL=/bin/bash kernel/locking/ kernel/rcu/
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:491: warning: expecting prototype for rwsem_rt_mutex_try_lock_nolockdep(). Prototype was for rwsem_rt_mutex_trylock() instead
vim +491 kernel/locking/rtmutex_api.c
481
482 /**
483 * rwsem_rt_mutex_try_lock_nolockdep - Try to lock a rt_mutex
484 * @lock: The rt_mutex to be locked
485 *
486 * The function does no lockdep operations on @lock. The lockdep state
487 * changes have to be done on the callsite related to the locking primitive
488 * which embeds the rtmutex. Otherwise lockdep has double tracking.
489 */
490 int __sched rwsem_rt_mutex_trylock(struct rt_mutex *lock)
> 491 {
492 if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEXES) &&
493 WARN_ON_ONCE(in_nmi() | in_hardirq()))
494 return 0;
495
496 if (likely(rt_mutex_cmpxchg_acquire(lock, NULL, current)))
497 return 1;
498
499 return rt_mutex_slowtrylock(lock);
500 }
501
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 73411 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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-rebase 95/222] kernel/locking/rtmutex_api.c:491: warning: expecting prototype for rwsem_rt_mutex_try_lock_nolockdep(). Prototype was for rwsem_rt_mutex_trylock() instead
Date: Thu, 8 Jul 2021 20:53:18 +0800 [thread overview]
Message-ID: <202107082005.N22r0YHL-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.13.y-rt-rebase
head: 7e175e6b59975c8901ad370f7818937f68de45c1
commit: e03cbdcf154eddbc014705b6e2ebacd755d6ab39 [95/222] locking/rtmutex: Provide lockdep less variants of rtmutex interfaces
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-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=e03cbdcf154eddbc014705b6e2ebacd755d6ab39
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-rebase
git checkout e03cbdcf154eddbc014705b6e2ebacd755d6ab39
# 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=powerpc SHELL=/bin/bash kernel/locking/ kernel/rcu/
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:491: warning: expecting prototype for rwsem_rt_mutex_try_lock_nolockdep(). Prototype was for rwsem_rt_mutex_trylock() instead
vim +491 kernel/locking/rtmutex_api.c
481
482 /**
483 * rwsem_rt_mutex_try_lock_nolockdep - Try to lock a rt_mutex
484 * @lock: The rt_mutex to be locked
485 *
486 * The function does no lockdep operations on @lock. The lockdep state
487 * changes have to be done on the callsite related to the locking primitive
488 * which embeds the rtmutex. Otherwise lockdep has double tracking.
489 */
490 int __sched rwsem_rt_mutex_trylock(struct rt_mutex *lock)
> 491 {
492 if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEXES) &&
493 WARN_ON_ONCE(in_nmi() | in_hardirq()))
494 return 0;
495
496 if (likely(rt_mutex_cmpxchg_acquire(lock, NULL, current)))
497 return 1;
498
499 return rt_mutex_slowtrylock(lock);
500 }
501
---
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: 73411 bytes --]
next reply other threads:[~2021-07-08 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:53 kernel test robot [this message]
2021-07-08 12:53 ` [linux-rt-devel:linux-5.13.y-rt-rebase 95/222] kernel/locking/rtmutex_api.c:491: warning: expecting prototype for rwsem_rt_mutex_try_lock_nolockdep(). Prototype was for rwsem_rt_mutex_trylock() instead kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-07-08 15:14 kernel test robot
2021-07-08 15:14 ` 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=202107082005.N22r0YHL-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.