From: kernel test robot <lkp@intel.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Christoph Hellwig <hch@lst.de>
Subject: include/linux/spinlock.h:378:9: sparse: sparse: context imbalance in 'gather_surplus_pages' - unexpected unlock
Date: Fri, 26 Jun 2020 05:03:35 +0800 [thread overview]
Message-ID: <202006260525.eU2y27wW%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 52366a107bf0600cf366f5ff3ea1f147b285e41f
commit: 9e953cda5cdf1c230a3c9b7fc4d5e94f15885a9b riscv: Introduce huge page support for 32/64bit kernel
date: 12 months ago
config: riscv-randconfig-s031-20200624 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-dirty
git checkout 9e953cda5cdf1c230a3c9b7fc4d5e94f15885a9b
# 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 >>)
>> include/linux/spinlock.h:378:9: sparse: sparse: context imbalance in 'gather_surplus_pages' - unexpected unlock
include/linux/spinlock.h:378:9: sparse: sparse: context imbalance in 'hugetlb_cow' - unexpected unlock
mm/hugetlb.c:4323:25: sparse: sparse: context imbalance in 'follow_hugetlb_page' - different lock contexts for basic block
vim +/gather_surplus_pages +378 include/linux/spinlock.h
c2f21ce2e31286a Thomas Gleixner 2009-12-02 375
3490565b633c705 Denys Vlasenko 2015-07-13 376 static __always_inline void spin_unlock(spinlock_t *lock)
c2f21ce2e31286a Thomas Gleixner 2009-12-02 377 {
c2f21ce2e31286a Thomas Gleixner 2009-12-02 @378 raw_spin_unlock(&lock->rlock);
c2f21ce2e31286a Thomas Gleixner 2009-12-02 379 }
c2f21ce2e31286a Thomas Gleixner 2009-12-02 380
:::::: The code at line 378 was first introduced by commit
:::::: c2f21ce2e31286a0a32f8da0a7856e9ca1122ef3 locking: Implement new raw_spinlock
:::::: 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@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25838 bytes --]
reply other threads:[~2020-06-25 21:05 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=202006260525.eU2y27wW%lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.walmsley@sifive.com \
/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®