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 223/385] fs/bcachefs/data/reconcile/check.c:445:1: warning: the frame size of 1044 bytes is larger than 1024 bytes
Date: Mon, 23 Feb 2026 09:54:03 +0800 [thread overview]
Message-ID: <202602230940.IMnp6AX8-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs master
head: d4bd02beae9ffcc8e3c028b54cb3a25b06e95beb
commit: de374d7b7296203619ba70f976867051cebaf41b [223/385] bcachefs: Break up reconcile.c
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260223/202602230940.IMnp6AX8-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260223/202602230940.IMnp6AX8-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/202602230940.IMnp6AX8-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/bcachefs/data/reconcile/check.c: In function 'bch2_check_reconcile_work':
>> fs/bcachefs/data/reconcile/check.c:445:1: warning: the frame size of 1044 bytes is larger than 1024 bytes [-Wframe-larger-than=]
445 | }
| ^
vim +445 fs/bcachefs/data/reconcile/check.c
407
408 int bch2_check_reconcile_work(struct bch_fs *c)
409 {
410 CLASS(btree_trans, trans)(c);
411 CLASS(btree_iter_uninit, extent_iter)(trans);
412 CLASS(btree_iter, rb_w)(trans, BTREE_ID_reconcile_work, POS_MIN,
413 BTREE_ITER_prefetch|BTREE_ITER_all_snapshots);
414 CLASS(btree_iter, rb_h)(trans, BTREE_ID_reconcile_hipri, POS_MIN,
415 BTREE_ITER_prefetch|BTREE_ITER_all_snapshots);
416 CLASS(btree_iter, rb_p)(trans, BTREE_ID_reconcile_pending, POS_MIN,
417 BTREE_ITER_prefetch|BTREE_ITER_all_snapshots);
418
419 CLASS(per_snapshot_io_opts, snapshot_io_opts)(c);
420
421 struct wb_maybe_flush last_flushed __cleanup(wb_maybe_flush_exit);
422 wb_maybe_flush_init(&last_flushed);
423
424 struct progress_indicator progress;
425 bch2_progress_init(&progress, __func__, c,
426 BIT_ULL(BTREE_ID_extents)|
427 BIT_ULL(BTREE_ID_reflink),
428 0);
429
430 static const enum btree_id data_btrees[] = {
431 BTREE_ID_stripes,
432 BTREE_ID_reflink,
433 BTREE_ID_extents,
434 };
435 for (unsigned i = 0; i < ARRAY_SIZE(data_btrees); i++)
436 try(check_reconcile_work_data_btree(trans, data_btrees[i],
437 &rb_w, &rb_h, &rb_p,
438 &snapshot_io_opts, &progress, &last_flushed));
439
440 try(check_reconcile_work_phys(trans));
441 try(check_reconcile_work_btrees(trans));
442 try(check_reconcile_btree_bps(trans));
443
444 return 0;
> 445 }
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-23 1:54 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=202602230940.IMnp6AX8-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.