From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:fs-next 337/433] fs/bcachefs/btree_key_cache.c:758:9: sparse: sparse: dereference of noderef expression
Date: Thu, 22 Aug 2024 15:01:51 +0800 [thread overview]
Message-ID: <202408221407.KnZ1VF8O-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git fs-next
head: 7ba615b05fbe745265e898c3bf8db40453c59b8a
commit: f316d2e88651ba94dff468e038621a5385002b2d [337/433] bcachefs: Rip out freelists from btree key cache
config: csky-randconfig-r132-20240822 (https://download.01.org/0day-ci/archive/20240822/202408221407.KnZ1VF8O-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240822/202408221407.KnZ1VF8O-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202408221407.KnZ1VF8O-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/bcachefs/btree_key_cache.c: note: in included file:
fs/bcachefs/bcachefs.h:996:9: sparse: sparse: array of flexible structures
fs/bcachefs/btree_key_cache.c:687:32: sparse: sparse: context imbalance in 'bch2_fs_btree_key_cache_exit' - different lock contexts for basic block
>> fs/bcachefs/btree_key_cache.c:758:9: sparse: sparse: dereference of noderef expression
vim +758 fs/bcachefs/btree_key_cache.c
750
751 void bch2_btree_key_cache_to_text(struct printbuf *out, struct btree_key_cache *bc)
752 {
753 printbuf_tabstop_push(out, 24);
754 printbuf_tabstop_push(out, 12);
755
756 prt_printf(out, "keys:\t%lu\r\n", atomic_long_read(&bc->nr_keys));
757 prt_printf(out, "dirty:\t%lu\r\n", atomic_long_read(&bc->nr_dirty));
> 758 prt_printf(out, "table size:\t%u\r\n", bc->table.tbl->size);
759
760 prt_printf(out, "\nshrinker:\n");
761 prt_printf(out, "requested_to_free:\t%lu\r\n", bc->requested_to_free);
762 prt_printf(out, "freed:\t%lu\r\n", bc->freed);
763 prt_printf(out, "skipped_dirty:\t%lu\r\n", bc->skipped_dirty);
764 prt_printf(out, "skipped_accessed:\t%lu\r\n", bc->skipped_accessed);
765 prt_printf(out, "skipped_lock_fail:\t%lu\r\n", bc->skipped_lock_fail);
766 }
767
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-22 7:02 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=202408221407.KnZ1VF8O-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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