syzbot


INFO: task hung in bch2_journal_reclaim_thread (2)

Status: upstream: reported C repro on 2024/09/21 08:21
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+820dc3b465c69f766a57@syzkaller.appspotmail.com
First crash: 426d, last: 42d
Cause bisection: introduced by (bisect log) :
commit b1d63b06e8398eb048dcc455acc628e6655d7499
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri Jun 28 22:10:47 2024 +0000

  bcachefs: Make read_only a mount option again, but hidden

Crash: INFO: task hung in bch2_journal_reclaim_thread (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (13)
Title Replies (including bot) Last reply
[syzbot] Monthly bcachefs report (Sep 2025) 0 (1) 2025/09/26 05:14
[syzbot] Monthly bcachefs report (Aug 2025) 0 (1) 2025/08/26 07:13
[syzbot] Monthly bcachefs report (Jul 2025) 0 (1) 2025/07/25 12:39
[syzbot] Monthly bcachefs report (Jun 2025) 2 (3) 2025/06/24 17:31
[syzbot] Monthly bcachefs report (May 2025) 0 (1) 2025/05/24 10:04
[syzbot] Monthly bcachefs report (Apr 2025) 0 (1) 2025/04/22 12:41
[syzbot] Monthly bcachefs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly bcachefs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly bcachefs report (Jan 2025) 0 (1) 2025/01/16 10:11
[syzbot] Monthly bcachefs report (Dec 2024) 0 (1) 2024/12/16 09:45
[syzbot] Monthly bcachefs report (Nov 2024) 0 (1) 2024/11/15 10:49
[syzbot] [bcachefs?] INFO: task hung in bch2_journal_reclaim_thread (2) 1 (5) 2024/10/26 05:18
[syzbot] Monthly bcachefs report (Oct 2024) 0 (1) 2024/10/14 19:38
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in bch2_journal_reclaim_thread bcachefs 1 1 493d 493d 0/29 auto-obsoleted due to no activity on 2024/09/06 07:24
Last patch testing requests (11)
Created Duration User Patch Repo Result
2025/10/16 17:50 22m retest repro upstream OK log
2025/10/16 17:49 45m retest repro linux-next OK log
2025/10/16 17:50 22m retest repro upstream OK log
2025/10/16 17:50 20m retest repro upstream OK log
2025/10/16 16:54 52m retest repro upstream OK log
2025/10/16 16:10 20m retest repro upstream OK log
2025/10/16 16:10 20m retest repro upstream log
2025/10/16 16:10 20m retest repro upstream OK log
2025/06/08 01:58 1h04m retest repro linux-next report log
2025/06/07 23:36 21m retest repro upstream OK log
2024/10/26 04:50 15m eadavis@qq.com patch upstream report log

Sample crash report:
INFO: task bch-reclaim/loo:6197 blocked for more than 143 seconds.
      Not tainted 6.14.0-rc1-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:bch-reclaim/loo state:D stack:26448 pid:6197  tgid:6197  ppid:2      task_flags:0x200040 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5377 [inline]
 __schedule+0x190e/0x4c90 kernel/sched/core.c:6764
 __schedule_loop kernel/sched/core.c:6841 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6856
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6913
 __mutex_lock_common kernel/locking/mutex.c:662 [inline]
 __mutex_lock+0x817/0x1010 kernel/locking/mutex.c:730
 bch2_journal_reclaim_thread+0x16d/0x570 fs/bcachefs/journal_reclaim.c:759
 kthread+0x7a9/0x920 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/25:
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6746
2 locks held by getty/5102:
 #0: ffff888000f910a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000019b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
6 locks held by syz-executor102/5331:
 #0: ffff888049e520e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff888049e520e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff888049e520e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505
 #1: ffff88804ba00278 (&c->state_lock){+.+.}-{4:4}, at: __bch2_fs_stop+0xfd/0x5c0 fs/bcachefs/super.c:622
 #2: ffff88804ba4b028 (&j->reclaim_lock){+.+.}-{4:4}, at: journal_flush_done+0x7b/0x400 fs/bcachefs/journal_reclaim.c:870
 #3: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #3: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #3: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x7e4/0xd30 fs/bcachefs/btree_iter.c:3377
 #4: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #4: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #4: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: bch2_trans_srcu_lock+0x9a/0x1a0 fs/bcachefs/btree_iter.c:3202
 #5: ffff88804ba266d0 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x682/0x14e0 fs/bcachefs/btree_update_interior.c:1180
4 locks held by kworker/u4:0/5512:
 #0: ffff888040b67148 ((wq_completion)btree_update){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff888040b67148 ((wq_completion)btree_update){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc9000e20fc60 ((work_completion)(&c->btree_interior_update_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc9000e20fc60 ((work_completion)(&c->btree_interior_update_work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #2: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #2: ffff88804ba04378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x7e4/0xd30 fs/bcachefs/btree_iter.c:3377
 #3: ffff88804ba266d0 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x682/0x14e0 fs/bcachefs/btree_update_interior.c:1180
1 lock held by bch-reclaim/loo/6197:
 #0: ffff88804ba4b028 (&j->reclaim_lock){+.+.}-{4:4}, at: bch2_journal_reclaim_thread+0x16d/0x570 fs/bcachefs/journal_reclaim.c:759
3 locks held by syz-executor102/8175:
 #0: ffff888043afda08 (&sb->s_type->i_mutex_key#10){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:865 [inline]
 #0: ffff888043afda08 (&sb->s_type->i_mutex_key#10){+.+.}-{4:4}, at: __sock_release net/socket.c:641 [inline]
 #0: ffff888043afda08 (&sb->s_type->i_mutex_key#10){+.+.}-{4:4}, at: sock_close+0x90/0x240 net/socket.c:1393
 #1: ffff888035b26258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1624 [inline]
 #1: ffff888035b26258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_release+0x790/0xcd0 net/packet/af_packet.c:3204
 #2: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:302 [inline]
 #2: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x381/0x830 kernel/rcu/tree_exp.h:996
2 locks held by syz-executor102/8178:
 #0: ffff888034cc4258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1624 [inline]
 #0: ffff888034cc4258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_setsockopt+0x754/0x1970 net/packet/af_packet.c:3872
 #1: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:334 [inline]
 #1: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x451/0x830 kernel/rcu/tree_exp.h:996
1 lock held by syz-executor102/8181:
 #0: ffff888043c90258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1624 [inline]
 #0: ffff888043c90258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_setsockopt+0x754/0x1970 net/packet/af_packet.c:3872
2 locks held by syz-executor102/8184:
4 locks held by syz-executor102/8189:

=============================================

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 25 Comm: khungtaskd Not tainted 6.14.0-rc1-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:236 [inline]
 watchdog+0x1058/0x10a0 kernel/hung_task.c:399
 kthread+0x7a9/0x920 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Crashes (1574):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/03 18:40 upstream 2014c95afece a21a8419 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/28 18:10 upstream 51a24b7deaae 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/28 12:58 upstream 51a24b7deaae 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/24 06:51 upstream cec1e6e5d1ab 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/24 05:44 upstream cec1e6e5d1ab 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/21 04:41 upstream 3b08f56fbbb9 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/20 09:09 upstream cd89d487374c 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/16 11:50 upstream 46a51f4f5eda e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/12 12:34 upstream 320475fbd590 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/10 16:02 upstream 9dd1835ecda5 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/09 12:29 upstream f777d1112ee5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/08 15:46 upstream 76eeb9b8de98 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/08 09:26 upstream 76eeb9b8de98 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/07 11:48 upstream b236920731dd d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/07 03:58 upstream b236920731dd d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/06 19:26 upstream d1d10cea0895 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/06 18:26 upstream d1d10cea0895 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/06 18:24 upstream d1d10cea0895 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/05 06:39 upstream 08b06c30a445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 20:47 upstream 08b06c30a445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 12:50 upstream b9a10f876409 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 11:19 upstream b9a10f876409 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 10:37 upstream b9a10f876409 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 08:23 upstream b9a10f876409 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 02:00 upstream ec299e4dc21e 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/08/20 23:17 upstream 41cd3fd15263 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/06/20 07:06 upstream 24770983ccfe ed3e87f7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/02/08 11:34 upstream 7ee983c850b4 ef44b750 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/06 01:28 upstream 5c8c229261f1 4dc70884 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] [mounted in repro #3] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2024/12/31 00:28 upstream ccb98ccef0e5 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2024/09/29 15:21 upstream 3efc57369a0c ba29ff75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2024/09/29 05:44 upstream 3efc57369a0c ba29ff75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2024/09/28 21:18 upstream ad46e8f95e93 ba29ff75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2024/09/21 05:01 upstream 1868f9d0260e 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2024/09/17 00:13 upstream adfc3ded5c33 49cf0773 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/02/06 00:39 upstream 92514ef226f5 577d049b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root INFO: task hung in bch2_journal_reclaim_thread
2025/02/02 13:41 upstream 69e858e0b8b2 568559e4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-snapshot-upstream-root INFO: task hung in bch2_journal_reclaim_thread
2024/11/15 04:56 upstream cfaaa7d010d1 f6ede3a3 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root INFO: task hung in bch2_journal_reclaim_thread
2025/10/02 16:07 linux-next 3b9b1f8df454 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/10/02 06:03 linux-next 3b9b1f8df454 a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/30 23:36 linux-next 3b9b1f8df454 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/30 06:46 linux-next 3b9b1f8df454 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/29 18:04 linux-next 3b9b1f8df454 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/29 01:49 linux-next 262858079afd 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/28 08:02 linux-next 262858079afd 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/24 19:29 linux-next b5a4da2c459f 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/24 19:14 linux-next b5a4da2c459f 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/12 09:51 linux-next 590b221ed425 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/12 00:11 linux-next 5f540c4aade9 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/10 23:46 linux-next 5f540c4aade9 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/10 20:41 linux-next 5f540c4aade9 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/10 19:10 linux-next 5f540c4aade9 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/09 00:44 linux-next 3e8e5822146b d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/08 19:49 linux-next 3e8e5822146b d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/08 18:37 linux-next 3e8e5822146b d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/06 00:17 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/05 17:42 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/05 11:49 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 00:59 linux-next 5d50cf9f7cf2 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/04 00:22 linux-next 5d50cf9f7cf2 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/02/09 02:30 linux-next ed58d103e6da ef44b750 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in bch2_journal_reclaim_thread
2025/09/07 23:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b320789d6883 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in bch2_journal_reclaim_thread
2024/09/13 14:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci df54f4a16f82 73e8a465 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in bch2_journal_reclaim_thread
* Struck through repros no longer work on HEAD.