From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:trace_sched_wakeup_backtrace 249/332] fs/bcachefs/data/reconcile/work.c:1205:12: warning: stack frame size (1080) exceeds limit (1024) in 'bch2_reconcile_thread'
Date: Sat, 11 Apr 2026 00:25:06 +0800 [thread overview]
Message-ID: <202604110002.CsxNT0D9-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs trace_sched_wakeup_backtrace
head: 9e7cbd4ad9c7a7ba461dbba9185628c006e200cd
commit: 2df58c8935f572f91c66956583e5b764203df420 [249/332] bcachefs: Fix use-after-unlock in reconcile tracepoints
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260411/202604110002.CsxNT0D9-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260411/202604110002.CsxNT0D9-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/202604110002.CsxNT0D9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/bcachefs/data/reconcile/work.c:1205:12: warning: stack frame size (1080) exceeds limit (1024) in 'bch2_reconcile_thread' [-Wframe-larger-than]
1205 | static int bch2_reconcile_thread(void *arg)
| ^
fs/bcachefs/data/reconcile/work.c:980:25: warning: stack frame size (1216) exceeds limit (1024) in 'do_reconcile_phys_thread' [-Wframe-larger-than]
980 | static CLOSURE_CALLBACK(do_reconcile_phys_thread)
| ^
2 warnings generated.
vim +/bch2_reconcile_thread +1205 fs/bcachefs/data/reconcile/work.c
de374d7b729620 Kent Overstreet 2026-01-19 1204
de374d7b729620 Kent Overstreet 2026-01-19 @1205 static int bch2_reconcile_thread(void *arg)
de374d7b729620 Kent Overstreet 2026-01-19 1206 {
de374d7b729620 Kent Overstreet 2026-01-19 1207 struct bch_fs *c = arg;
de374d7b729620 Kent Overstreet 2026-01-19 1208 struct bch_fs_reconcile *r = &c->reconcile;
de374d7b729620 Kent Overstreet 2026-01-19 1209
de374d7b729620 Kent Overstreet 2026-01-19 1210 set_freezable();
de374d7b729620 Kent Overstreet 2026-01-19 1211
de374d7b729620 Kent Overstreet 2026-01-19 1212 /*
de374d7b729620 Kent Overstreet 2026-01-19 1213 * Data move operations can't run until after check_snapshots has
de374d7b729620 Kent Overstreet 2026-01-19 1214 * completed, and bch2_snapshot_is_ancestor() is available.
de374d7b729620 Kent Overstreet 2026-01-19 1215 */
de374d7b729620 Kent Overstreet 2026-01-19 1216 kthread_wait_freezable(c->recovery.pass_done > BCH_RECOVERY_PASS_check_snapshots ||
de374d7b729620 Kent Overstreet 2026-01-19 1217 kthread_should_stop());
de374d7b729620 Kent Overstreet 2026-01-19 1218 if (kthread_should_stop())
de374d7b729620 Kent Overstreet 2026-01-19 1219 return 0;
de374d7b729620 Kent Overstreet 2026-01-19 1220
de374d7b729620 Kent Overstreet 2026-01-19 1221 struct moving_context ctxt __cleanup(bch2_moving_ctxt_exit);
de374d7b729620 Kent Overstreet 2026-01-19 1222 bch2_moving_ctxt_init(&ctxt, c, NULL, &r->work_stats,
de374d7b729620 Kent Overstreet 2026-01-19 1223 writepoint_ptr(&c->allocator.reconcile_write_point),
de374d7b729620 Kent Overstreet 2026-01-19 1224 true);
de374d7b729620 Kent Overstreet 2026-01-19 1225
de374d7b729620 Kent Overstreet 2026-01-19 1226 while (!kthread_should_stop() && !do_reconcile(&ctxt))
de374d7b729620 Kent Overstreet 2026-01-19 1227 ;
de374d7b729620 Kent Overstreet 2026-01-19 1228
de374d7b729620 Kent Overstreet 2026-01-19 1229 return 0;
de374d7b729620 Kent Overstreet 2026-01-19 1230 }
de374d7b729620 Kent Overstreet 2026-01-19 1231
:::::: The code at line 1205 was first introduced by commit
:::::: de374d7b7296203619ba70f976867051cebaf41b bcachefs: Break up reconcile.c
:::::: 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-04-10 16:26 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=202604110002.CsxNT0D9-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=llvm@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox