From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: include/linux/spinlock_api_smp.h:151:27: sparse: sparse: context imbalance in 'orangefs_devreq_read' - different lock contexts for basic block
Date: Thu, 12 Nov 2020 00:46:45 +0800 [thread overview]
Message-ID: <202011120032.MtiWjXsq-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2939 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
CC: Cezary Rojewski <cezary.rojewski@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: eccc876724927ff3b9ff91f36f7b6b159e948f0c
commit: e130816164e244b692921de49771eeb28205152d include/linux/list.h: add a macro to test if entry is pointing to the head
date: 4 weeks ago
:::::: branch date: 22 hours ago
:::::: commit date: 4 weeks ago
config: powerpc-randconfig-s032-20201109 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-106-gd020cf33-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e130816164e244b692921de49771eeb28205152d
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout e130816164e244b692921de49771eeb28205152d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
fs/orangefs/devorangefs-req.c: note: in included file (through include/linux/spinlock.h, include/linux/mmzone.h, include/linux/gfp.h, ...):
>> include/linux/spinlock_api_smp.h:151:27: sparse: sparse: context imbalance in 'orangefs_devreq_read' - different lock contexts for basic block
vim +/orangefs_devreq_read +151 include/linux/spinlock_api_smp.h
69d0ee7377eef80 Heiko Carstens 2009-08-31 147
9c1721aa4994f66 Thomas Gleixner 2009-12-03 148 static inline void __raw_spin_unlock(raw_spinlock_t *lock)
69d0ee7377eef80 Heiko Carstens 2009-08-31 149 {
5facae4f3549b5c Qian Cai 2019-09-19 150 spin_release(&lock->dep_map, _RET_IP_);
9828ea9d75c38fe Thomas Gleixner 2009-12-03 @151 do_raw_spin_unlock(lock);
69d0ee7377eef80 Heiko Carstens 2009-08-31 152 preempt_enable();
69d0ee7377eef80 Heiko Carstens 2009-08-31 153 }
69d0ee7377eef80 Heiko Carstens 2009-08-31 154
:::::: The code at line 151 was first introduced by commit
:::::: 9828ea9d75c38fe3dce05d00566eed61c85732e6 locking: Further name space cleanups
:::::: 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(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24405 bytes --]
next reply other threads:[~2020-11-11 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 16:46 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-12 8:05 include/linux/spinlock_api_smp.h:151:27: sparse: sparse: context imbalance in 'orangefs_devreq_read' - different lock contexts for basic block kernel test robot
2020-11-12 7:26 kernel test robot
2020-11-11 20:58 kernel test robot
2020-11-11 20:28 kernel test robot
2020-11-11 19:58 kernel test robot
2020-11-11 17:48 kernel test robot
2020-11-11 13:06 kernel test robot
2020-11-11 12:19 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=202011120032.MtiWjXsq-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.