From: kernel test robot <lkp@intel.com>
To: ProofOfConcept <poc@bcachefs.org>
Cc: oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:bcachefs-testing 54/101] fs/bcachefs/alloc/check.c:606:1: warning: the frame size of 1584 bytes is larger than 1536 bytes
Date: Sun, 13 Sep 2026 19:18:33 +0200 [thread overview]
Message-ID: <202609131905.WKeVUgwe-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: ca944a61e079450f82be88c91e349638c75cf4b6
commit: fe43d8a0c1bbefdea2776bd64851ae18a2f1abc7 [54/101] bcachefs: Reindex need_discard btree by journal seq
config: xtensa-allyesconfig (https://download.01.org/0day-ci/archive/20260913/202609131905.WKeVUgwe-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260913/202609131905.WKeVUgwe-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/202609131905.WKeVUgwe-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/bcachefs/alloc/check.c: In function 'check_btree_alloc':
>> fs/bcachefs/alloc/check.c:606:1: warning: the frame size of 1584 bytes is larger than 1536 bytes [-Wframe-larger-than=]
606 | }
| ^
vim +606 fs/bcachefs/alloc/check.c
3fdc7b4035515f7 Kent Overstreet 2025-10-04 579
f066f962fcae77d Kent Overstreet 2025-11-09 580 static int check_btree_alloc(struct btree_trans *trans)
f066f962fcae77d Kent Overstreet 2025-11-09 581 {
f066f962fcae77d Kent Overstreet 2025-11-09 582 struct progress_indicator progress;
f89dd8a7c48ba10 Kent Overstreet 2025-11-30 583 bch2_progress_init(&progress, __func__, trans->c, BIT_ULL(BTREE_ID_alloc), 0);
f066f962fcae77d Kent Overstreet 2025-11-09 584
f066f962fcae77d Kent Overstreet 2025-11-09 585 CLASS(btree_iter, iter)(trans, BTREE_ID_alloc, POS_MIN, BTREE_ITER_prefetch);
f066f962fcae77d Kent Overstreet 2025-11-09 586 CLASS(btree_iter, discard_iter)(trans, BTREE_ID_need_discard, POS_MIN, BTREE_ITER_prefetch);
f066f962fcae77d Kent Overstreet 2025-11-09 587 CLASS(btree_iter, freespace_iter)(trans, BTREE_ID_freespace, POS_MIN, BTREE_ITER_prefetch);
f066f962fcae77d Kent Overstreet 2025-11-09 588 CLASS(btree_iter, bucket_gens_iter)(trans, BTREE_ID_bucket_gens, POS_MIN, BTREE_ITER_prefetch);
f066f962fcae77d Kent Overstreet 2025-11-09 589
fe43d8a0c1bbefd ProofOfConcept 2026-03-19 590 struct wb_maybe_flush last_flushed __cleanup(wb_maybe_flush_exit);
fe43d8a0c1bbefd ProofOfConcept 2026-03-19 591 wb_maybe_flush_init(&last_flushed);
fe43d8a0c1bbefd ProofOfConcept 2026-03-19 592
f066f962fcae77d Kent Overstreet 2025-11-09 593 struct bch_dev *ca __free(bch2_dev_put) = NULL;
f066f962fcae77d Kent Overstreet 2025-11-09 594 int ret = 0;
f066f962fcae77d Kent Overstreet 2025-11-09 595
f066f962fcae77d Kent Overstreet 2025-11-09 596 while (!(ret = lockrestart_do(trans,
f066f962fcae77d Kent Overstreet 2025-11-09 597 check_btree_alloc_iter(trans, &ca, &iter,
f066f962fcae77d Kent Overstreet 2025-11-09 598 &discard_iter,
f066f962fcae77d Kent Overstreet 2025-11-09 599 &freespace_iter,
f066f962fcae77d Kent Overstreet 2025-11-09 600 &bucket_gens_iter,
fe43d8a0c1bbefd ProofOfConcept 2026-03-19 601 &progress,
fe43d8a0c1bbefd ProofOfConcept 2026-03-19 602 &last_flushed))))
f066f962fcae77d Kent Overstreet 2025-11-09 603 ;
f066f962fcae77d Kent Overstreet 2025-11-09 604
0496470fb608956 Kent Overstreet 2025-10-24 605 return min(0, ret);
0496470fb608956 Kent Overstreet 2025-10-24 @606 }
0496470fb608956 Kent Overstreet 2025-10-24 607
:::::: The code at line 606 was first introduced by commit
:::::: 0496470fb6089562784d996d0fa12a611ef08029 bcachefs: Break up bch2_check_alloc_info()
:::::: 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:[~2026-09-13 17:19 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=202609131905.WKeVUgwe-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=poc@bcachefs.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 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.