From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 3504/6488] arch/riscv/include/asm/irqflags.h:22:9: sparse: sparse: context imbalance in 'pci_wait_cfg' - unexpected unlock
Date: Thu, 09 Jul 2020 03:04:52 +0800 [thread overview]
Message-ID: <202007090348.ixxehtSF%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8903263671cb22bc33545eb7cbd68c875bb87e95
commit: f3691b7ba5c39508aaac341050e72304bb1a115d [3504/6488] PCI: Fix pci_cfg_wait queue locking problem
config: riscv-randconfig-s031-20200708 (attached as .config)
compiler: riscv64-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.2-37-gc9676a3b-dirty
git checkout f3691b7ba5c39508aaac341050e72304bb1a115d
# 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=riscv
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 >>)
>> arch/riscv/include/asm/irqflags.h:22:9: sparse: sparse: context imbalance in 'pci_wait_cfg' - unexpected unlock
vim +/pci_wait_cfg +22 arch/riscv/include/asm/irqflags.h
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 18
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 19 /* unconditionally enable interrupts */
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 20 static inline void arch_local_irq_enable(void)
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 21 {
a4c3733d32a72f Christoph Hellwig 2019-10-28 @22 csr_set(CSR_STATUS, SR_IE);
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 23 }
6d60b6ee0c9777 Palmer Dabbelt 2017-07-10 24
:::::: The code at line 22 was first introduced by commit
:::::: a4c3733d32a72f11dee86d0731d7565aa6ebe22d riscv: abstract out CSR names for supervisor vs machine mode
:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Paul Walmsley <paul.walmsley@sifive.com>
---
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: 29925 bytes --]
reply other threads:[~2020-07-08 19:04 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=202007090348.ixxehtSF%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.