From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [bcache:nvdimm-meta 16/16] drivers/md/bcache/journal.c:904:13: sparse: sparse: context imbalance in 'journal_write' - wrong count at exit
Date: Fri, 09 Apr 2021 05:17:42 +0800 [thread overview]
Message-ID: <202104090533.5HOgVG2I-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3023 bytes --]
CC: kbuild-all(a)lists.01.org
TO: Coly Li <colyli@suse.de>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git nvdimm-meta
head: 722ffe14d3ec1009a9245b0f0ba49805643d92bb
commit: 722ffe14d3ec1009a9245b0f0ba49805643d92bb [16/16] bcache: more fix for compiling error when BCACHE_NVM_PAGES disabled
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: i386-randconfig-s002-20210408 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-279-g6d5d9b42-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git/commit/?id=722ffe14d3ec1009a9245b0f0ba49805643d92bb
git remote add bcache https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git
git fetch --no-tags bcache nvdimm-meta
git checkout 722ffe14d3ec1009a9245b0f0ba49805643d92bb
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
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/md/bcache/journal.c: note: in included file (through drivers/md/bcache/bcache.h):
include/uapi/linux/bcache.h:362:38: sparse: sparse: array of flexible structures
drivers/md/bcache/journal.c: note: in included file (through drivers/md/bcache/bcache.h):
drivers/md/bcache/bset.h:231:36: sparse: sparse: array of flexible structures
drivers/md/bcache/journal.c:875:17: sparse: sparse: context imbalance in 'journal_write_unlocked' - unexpected unlock
>> drivers/md/bcache/journal.c:904:13: sparse: sparse: context imbalance in 'journal_write' - wrong count at exit
drivers/md/bcache/journal.c:920:9: sparse: sparse: context imbalance in 'journal_try_write' - different lock contexts for basic block
vim +/journal_write +904 drivers/md/bcache/journal.c
cafe563591446c Kent Overstreet 2013-03-23 903
cafe563591446c Kent Overstreet 2013-03-23 @904 static void journal_write(struct closure *cl)
cafe563591446c Kent Overstreet 2013-03-23 905 {
7857d5d470ec53 Kent Overstreet 2013-10-08 906 struct cache_set *c = container_of(cl, struct cache_set, journal.io);
cafe563591446c Kent Overstreet 2013-03-23 907
cafe563591446c Kent Overstreet 2013-03-23 908 spin_lock(&c->journal.lock);
cafe563591446c Kent Overstreet 2013-03-23 909 journal_write_unlocked(cl);
cafe563591446c Kent Overstreet 2013-03-23 910 }
cafe563591446c Kent Overstreet 2013-03-23 911
:::::: The code at line 904 was first introduced by commit
:::::: cafe563591446cf80bfbc2fe3bc72a2e36cf1060 bcache: A block layer cache
:::::: TO: Kent Overstreet <koverstreet@google.com>
:::::: CC: Kent Overstreet <koverstreet@google.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: 35099 bytes --]
reply other threads:[~2021-04-08 21:17 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=202104090533.5HOgVG2I-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.