From: kbuild test robot <lkp@intel.com>
To: "Will, Deacon," <will@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: include/linux/compiler.h:199:9: sparse: sparse: context imbalance in 'alua_rtpg' - different lock contexts for basic block
Date: Tue, 2 Jun 2020 12:48:07 +0800 [thread overview]
Message-ID: <202006021203.hh90Z7PZ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f359287765c04711ff54fbd11645271d8e5ff763
commit: fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca locking/refcount: Consolidate implementations of refcount_t
date: 6 months ago
config: ia64-randconfig-s032-20200602 (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-243-gc100a7ab-dirty
git checkout fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca
# save the attached .config to linux build tree
make W=1 C=1 ARCH=ia64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> include/linux/compiler.h:199:9: sparse: sparse: context imbalance in 'alua_rtpg' - different lock contexts for basic block
vim +/alua_rtpg +199 include/linux/compiler.h
d976441f44bc5d4 Andrey Ryabinin 2015-10-19 195
d976441f44bc5d4 Andrey Ryabinin 2015-10-19 196 static __always_inline
d976441f44bc5d4 Andrey Ryabinin 2015-10-19 197 void __read_once_size(const volatile void *p, void *res, int size)
230fa253df6352a Christian Borntraeger 2014-11-25 198 {
d976441f44bc5d4 Andrey Ryabinin 2015-10-19 @199 __READ_ONCE_SIZE;
230fa253df6352a Christian Borntraeger 2014-11-25 200 }
d976441f44bc5d4 Andrey Ryabinin 2015-10-19 201
:::::: The code at line 199 was first introduced by commit
:::::: d976441f44bc5d48635d081d277aa76556ffbf8b compiler, atomics, kasan: Provide READ_ONCE_NOCHECK()
:::::: TO: Andrey Ryabinin <aryabinin@virtuozzo.com>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
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: 29943 bytes --]
reply other threads:[~2020-06-02 4:55 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=202006021203.hh90Z7PZ%lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=will@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®