From: kernel test robot <lkp@intel.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2:for-next.bob6b 5/12] include/asm-generic/atomic.h:142:1: sparse: sparse: context imbalance in 'gfs2_remove_from_journal' - different lock contexts for basic block
Date: Sun, 2 Aug 2020 06:23:49 +0800 [thread overview]
Message-ID: <202008020645.Ne4a9sj9%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next.bob6b
head: 8aef3eb9d3f560027f23e9690d0eca9427ba520d
commit: 338462527fad3a08cda656c2cc2f44d9ae319e42 [5/12] gfs2: Wipe jdata and ail1 in gfs2_journal_wipe, formerly gfs2_meta_wipe
config: c6x-randconfig-s032-20200802 (attached as .config)
compiler: c6x-elf-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-115-g5fc204f2-dirty
git checkout 338462527fad3a08cda656c2cc2f44d9ae319e42
# 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=c6x
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 >>)
fs/gfs2/meta_io.c: note: in included file (through arch/c6x/include/generated/asm/atomic.h, include/linux/atomic.h, include/asm-generic/bitops/lock.h, ...):
>> include/asm-generic/atomic.h:142:1: sparse: sparse: context imbalance in 'gfs2_remove_from_journal' - different lock contexts for basic block
vim +/gfs2_remove_from_journal +142 include/asm-generic/atomic.h
28aa2bda2211f43 Peter Zijlstra 2016-04-18 140
56d1defe0bbddaa Peter Zijlstra 2015-07-15 141 #ifndef atomic_and
560cb12a4080a48 Peter Zijlstra 2014-04-23 @142 ATOMIC_OP(and, &)
56d1defe0bbddaa Peter Zijlstra 2015-07-15 143 #endif
56d1defe0bbddaa Peter Zijlstra 2015-07-15 144
:::::: The code at line 142 was first introduced by commit
:::::: 560cb12a4080a48b84da8b96878cafbd193c4d64 locking,arch: Rewrite generic atomic support
:::::: 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 at lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 22329 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20200802/b53b2520/attachment.gz>
reply other threads:[~2020-08-01 22:23 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=202008020645.Ne4a9sj9%lkp@intel.com \
--to=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).