From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:bcachefs-testing 97/97] fs/bcachefs/btree_iter.c:3411:83: error: 'ck' undeclared; did you mean 'c'?
Date: Mon, 10 Jun 2024 04:43:51 +0800 [thread overview]
Message-ID: <202406100438.HAWNbcex-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: e514088a9cf20c9729c12fb6cf92de291fb7cca6
commit: e514088a9cf20c9729c12fb6cf92de291fb7cca6 [97/97] debug per paul
config: i386-buildonly-randconfig-002-20240610 (https://download.01.org/0day-ci/archive/20240610/202406100438.HAWNbcex-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240610/202406100438.HAWNbcex-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/202406100438.HAWNbcex-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/x86/include/asm/bug.h:87,
from include/linux/bug.h:5,
from include/linux/fortify-string.h:6,
from include/linux/string.h:374,
from include/linux/bitmap.h:13,
from include/linux/cpumask.h:13,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/radix-tree.h:14,
from include/linux/backing-dev-defs.h:6,
from fs/bcachefs/bcachefs.h:186,
from fs/bcachefs/btree_iter.c:3:
fs/bcachefs/btree_iter.c: In function 'bch2_fs_btree_iter_exit':
>> fs/bcachefs/btree_iter.c:3411:83: error: 'ck' undeclared (first use in this function); did you mean 'c'?
3411 | WARN_ON_ONCE(poll_state_synchronize_srcu(&c->btree_trans_barrier, ck->btree_trans_barrier_seq));
| ^~
include/asm-generic/bug.h:111:32: note: in definition of macro 'WARN_ON_ONCE'
111 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
fs/bcachefs/btree_iter.c:3411:83: note: each undeclared identifier is reported only once for each function it appears in
3411 | WARN_ON_ONCE(poll_state_synchronize_srcu(&c->btree_trans_barrier, ck->btree_trans_barrier_seq));
| ^~
include/asm-generic/bug.h:111:32: note: in definition of macro 'WARN_ON_ONCE'
111 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
vim +3411 fs/bcachefs/btree_iter.c
3376
3377 void bch2_fs_btree_iter_exit(struct bch_fs *c)
3378 {
3379 struct btree_transaction_stats *s;
3380 struct btree_trans *trans;
3381 int cpu;
3382
3383 if (c->btree_trans_bufs)
3384 for_each_possible_cpu(cpu) {
3385 struct btree_trans *trans =
3386 per_cpu_ptr(c->btree_trans_bufs, cpu)->trans;
3387
3388 if (trans) {
3389 closure_sync(&trans->ref);
3390
3391 seqmutex_lock(&c->btree_trans_lock);
3392 list_del(&trans->list);
3393 seqmutex_unlock(&c->btree_trans_lock);
3394 }
3395 kfree(trans);
3396 }
3397 free_percpu(c->btree_trans_bufs);
3398
3399 trans = list_first_entry_or_null(&c->btree_trans_list, struct btree_trans, list);
3400 if (trans)
3401 panic("%s leaked btree_trans\n", trans->fn);
3402
3403 for (s = c->btree_transaction_stats;
3404 s < c->btree_transaction_stats + ARRAY_SIZE(c->btree_transaction_stats);
3405 s++) {
3406 kfree(s->max_paths_text);
3407 bch2_time_stats_exit(&s->lock_hold_times);
3408 }
3409
3410 if (c->btree_trans_barrier_initialized) {
> 3411 WARN_ON_ONCE(poll_state_synchronize_srcu(&c->btree_trans_barrier, ck->btree_trans_barrier_seq));
3412 cleanup_srcu_struct(&c->btree_trans_barrier);
3413 }
3414 mempool_exit(&c->btree_trans_mem_pool);
3415 mempool_exit(&c->btree_trans_pool);
3416 }
3417
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-09 20:44 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=202406100438.HAWNbcex-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.