From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: arch/ia64/include/asm/atomic.h:65:1: sparse: sparse: context imbalance in 'alua_rtpg' - different lock contexts for basic block
Date: Fri, 26 Feb 2021 20:20:45 +0800 [thread overview]
Message-ID: <202102262041.ooEYgdor-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3016 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Mark Rutland <mark.rutland@arm.com>
CC: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2c87f7a38f930ef6f6a7bdd04aeb82ce3971b54b
commit: 997acaf6b4b59c6a9c259740312a69ea549cc684 lockdep: report broken irq restoration
date: 5 weeks ago
:::::: branch date: 16 hours ago
:::::: commit date: 5 weeks ago
config: ia64-randconfig-s031-20210226 (attached as .config)
compiler: ia64-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-241-geaceeafa-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=997acaf6b4b59c6a9c259740312a69ea549cc684
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 997acaf6b4b59c6a9c259740312a69ea549cc684
# 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=ia64
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 >>)"
drivers/scsi/device_handler/scsi_dh_alua.c: note: in included file (through include/linux/atomic.h, arch/ia64/include/asm/processor.h, arch/ia64/include/asm/thread_info.h, ...):
>> arch/ia64/include/asm/atomic.h:65:1: sparse: sparse: context imbalance in 'alua_rtpg' - different lock contexts for basic block
vim +/alua_rtpg +65 arch/ia64/include/asm/atomic.h
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 59
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 60 #define ATOMIC_OPS(op, c_op) \
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 61 ATOMIC_OP(op, c_op) \
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 62 ATOMIC_FETCH_OP(op, c_op)
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 63
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 64 ATOMIC_OPS(add, +)
cc102507fac75f arch/ia64/include/asm/atomic.h Peter Zijlstra 2016-04-18 @65 ATOMIC_OPS(sub, -)
^1da177e4c3f41 include/asm-ia64/atomic.h Linus Torvalds 2005-04-16 66
:::::: The code at line 65 was first introduced by commit
:::::: cc102507fac75f9f4f37938f49d10c25e596a608 locking/atomic, arch/ia64: Implement atomic{,64}_fetch_{add,sub,and,or,xor}()
:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
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: 34740 bytes --]
reply other threads:[~2021-02-26 12:20 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=202102262041.ooEYgdor-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.