From: kernel test robot <lkp@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: kbuild-all@lists.01.org, linux-btrfs@vger.kernel.org
Subject: [josef-btrfs:locking-rework 16/18] include/trace/events/btrfs.h:2066:1: sparse: sparse: context imbalance in '__btrfs_tree_lock' - wrong count at exit
Date: Tue, 11 Aug 2020 02:19:53 +0800 [thread overview]
Message-ID: <202008110251.ADpOhQOt%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git locking-rework
head: ecc26315fec63c1ce9a1420cb6d9b6e0d0c4d7f5
commit: 061e82bf86d54d981acb307eff1fa114e71c3854 [16/18] btrfs: change our extent buffer lock to a rw_semaphore
config: i386-randconfig-s002-20200810 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-141-g19506bc2-dirty
git checkout 061e82bf86d54d981acb307eff1fa114e71c3854
# 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 >>)
fs/btrfs/locking.c: note: in included file (through fs/btrfs/ctree.h):
>> include/trace/events/btrfs.h:2066:1: sparse: sparse: context imbalance in '__btrfs_tree_lock' - wrong count at exit
fs/btrfs/locking.c:217:6: sparse: sparse: context imbalance in 'btrfs_tree_lock' - wrong count at exit
vim +/__btrfs_tree_lock +2066 include/trace/events/btrfs.h
34e73cc930a867 Qu Wenruo 2019-04-15 2065
34e73cc930a867 Qu Wenruo 2019-04-15 @2066 DEFINE_EVENT(btrfs_sleep_tree_lock, btrfs_tree_lock,
34e73cc930a867 Qu Wenruo 2019-04-15 2067 TP_PROTO(const struct extent_buffer *eb, u64 start_ns),
34e73cc930a867 Qu Wenruo 2019-04-15 2068
34e73cc930a867 Qu Wenruo 2019-04-15 2069 TP_ARGS(eb, start_ns)
34e73cc930a867 Qu Wenruo 2019-04-15 2070 );
34e73cc930a867 Qu Wenruo 2019-04-15 2071
:::::: The code at line 2066 was first introduced by commit
:::::: 34e73cc930a8677426c9cbffdd3421e18f32e79f btrfs: trace: Introduce trace events for sleepable tree lock
:::::: TO: Qu Wenruo <wqu@suse.com>
:::::: CC: David Sterba <dsterba@suse.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: 35389 bytes --]
reply other threads:[~2020-08-10 18:49 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=202008110251.ADpOhQOt%lkp@intel.com \
--to=lkp@intel.com \
--cc=josef@toxicpanda.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-btrfs@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