mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Leon Romanovsky <leonro@mellanox.com>
Subject: arch/riscv/include/asm/irqflags.h:22:9: sparse: sparse: context imbalance in 'cm_queue_work_unlock' - unexpected unlock
Date: Fri, 19 Jun 2020 16:58:03 +0800	[thread overview]
Message-ID: <202006191658.uKz7JabB%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3433 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   5e857ce6eae7ca21b2055cca4885545e29228fe2
commit: e83f195aa45c1ffd73b3a950a887e41c260cf194 RDMA/cm: Pull duplicated code into cm_queue_work_unlock()
date:   5 weeks ago
config: riscv-randconfig-s032-20200619 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.2-rc1-18-g27caae40-dirty
        git checkout e83f195aa45c1ffd73b3a950a887e41c260cf194
        # save the attached .config to linux build tree
        make W=1 C=1 ARCH=riscv CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

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/infiniband/core/cm.c:1297:21: sparse: sparse: cast from restricted __be32
>> arch/riscv/include/asm/irqflags.h:22:9: sparse: sparse: context imbalance in 'cm_queue_work_unlock' - unexpected unlock
   drivers/infiniband/core/cm.c:2043:12: sparse: sparse: context imbalance in 'cm_req_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2422:12: sparse: sparse: context imbalance in 'cm_rep_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2533:12: sparse: sparse: context imbalance in 'cm_establish_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2556:12: sparse: sparse: context imbalance in 'cm_rtu_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2770:12: sparse: sparse: context imbalance in 'cm_dreq_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2847:12: sparse: sparse: context imbalance in 'cm_drep_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:2995:12: sparse: sparse: context imbalance in 'cm_rej_handler' - wrong count at exit
   drivers/infiniband/core/cm.c:3153:12: sparse: sparse: context imbalance in 'cm_mra_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:3271:12: sparse: sparse: context imbalance in 'cm_lap_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:3360:12: sparse: sparse: context imbalance in 'cm_apr_handler' - different lock contexts for basic block
   drivers/infiniband/core/cm.c:3405:12: sparse: sparse: context imbalance in 'cm_timewait_handler' - different lock contexts for basic block

vim +/cm_queue_work_unlock +22 arch/riscv/include/asm/irqflags.h

6d60b6ee0c9777b Palmer Dabbelt    2017-07-10  18  
6d60b6ee0c9777b Palmer Dabbelt    2017-07-10  19  /* unconditionally enable interrupts */
6d60b6ee0c9777b Palmer Dabbelt    2017-07-10  20  static inline void arch_local_irq_enable(void)
6d60b6ee0c9777b Palmer Dabbelt    2017-07-10  21  {
a4c3733d32a72f1 Christoph Hellwig 2019-10-28 @22  	csr_set(CSR_STATUS, SR_IE);
6d60b6ee0c9777b Palmer Dabbelt    2017-07-10  23  }
6d60b6ee0c9777b 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@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25361 bytes --]

                 reply	other threads:[~2020-06-19  8:58 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=202006191658.uKz7JabB%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jgg@mellanox.com \
    --cc=kbuild-all@lists.01.org \
    --cc=leonro@mellanox.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®