From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:master 458/672] fs/bcachefs/btree/commit.c:343:32-33: Unneeded semicolon
Date: Sun, 26 Oct 2025 20:32:44 +0800 [thread overview]
Message-ID: <202510262023.DFG8DRdF-lkp@intel.com> (raw)
Hi Kent,
First bad commit (maybe != root cause):
tree: https://github.com/koverstreet/bcachefs master
head: 232d5200c70baf66e106b70f6f54f6c234c2be46
commit: caf90d22262c52f7c29c4b08bd50f2a27d3dbe25 [458/672] bcachefs: move btree files to subdir
config: parisc-randconfig-r062-20251026 (https://download.01.org/0day-ci/archive/20251026/202510262023.DFG8DRdF-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
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/202510262023.DFG8DRdF-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> fs/bcachefs/btree/commit.c:343:32-33: Unneeded semicolon
vim +343 fs/bcachefs/btree/commit.c
1c6fdbd8f2465d fs/bcachefs/btree_update_leaf.c Kent Overstreet 2017-03-16 333
1a470560c9ab8d fs/bcachefs/btree_update_leaf.c Kent Overstreet 2019-03-18 334 static inline void btree_insert_entry_checks(struct btree_trans *trans,
6333bd2f133459 fs/bcachefs/btree_update_leaf.c Kent Overstreet 2021-02-20 335 struct btree_insert_entry *i)
1c6fdbd8f2465d fs/bcachefs/btree_update_leaf.c Kent Overstreet 2017-03-16 336 {
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 337 struct btree_path *path = trans->paths + i->path;
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 338
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 339 BUG_ON(!bpos_eq(i->k->k.p, path->pos));
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 340 BUG_ON(i->cached != path->cached);
54582f52ed7a63 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2025-06-24 341 BUG_ON(i->cached &&
54582f52ed7a63 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2025-06-24 342 !i->key_cache_already_flushed &&
54582f52ed7a63 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2025-06-24 @343 bkey_deleted(&i->k->k));;
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 344 BUG_ON(i->level != path->level);
7f9821a7c10bca fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-12-10 345 BUG_ON(i->btree_id != path->btree_id);
65bc7688b8feb5 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2025-02-11 346 BUG_ON(i->bkey_type != __btree_node_type(path->level, path->btree_id));
14b393ee768e83 fs/bcachefs/btree_update_leaf.c Kent Overstreet 2021-03-16 347 EBUG_ON(!i->level &&
d3c7727bb9269c fs/bcachefs/btree_trans_commit.c Kent Overstreet 2023-11-03 348 btree_type_has_snapshots(i->btree_id) &&
5dd8c60e1e0448 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2024-04-07 349 !(i->flags & BTREE_UPDATE_internal_snapshot_node) &&
b895c70326aa43 fs/bcachefs/btree_trans_commit.c Kent Overstreet 2024-04-30 350 test_bit(JOURNAL_replay_done, &trans->c->journal.flags) &&
14b393ee768e83 fs/bcachefs/btree_update_leaf.c Kent Overstreet 2021-03-16 351 i->k->k.p.snapshot &&
ec9cc18fc2e65b fs/bcachefs/btree_trans_commit.c Kent Overstreet 2024-03-22 352 bch2_snapshot_is_internal_node(trans->c, i->k->k.p.snapshot) > 0);
9623ab27ab27e2 fs/bcachefs/btree_update_leaf.c Kent Overstreet 2019-03-15 353 }
1c6fdbd8f2465d fs/bcachefs/btree_update_leaf.c Kent Overstreet 2017-03-16 354
:::::: The code at line 343 was first introduced by commit
:::::: 54582f52ed7a63a557308bd0a3efd0f5fc5443c6 bcachefs: Evict/bypass key cache when deleting
:::::: TO: Kent Overstreet <kent.overstreet@linux.dev>
:::::: CC: Kent Overstreet <kent.overstreet@linux.dev>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-26 12:33 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=202510262023.DFG8DRdF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--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 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.