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: 155d, last: 1h32m
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
  
Discussions (5)
Title Replies (including bot) Last reply
[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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in bch2_journal_reclaim_thread bcachefs 1 222d 222d 0/28 auto-obsoleted due to no activity on 2024/09/06 07:24
Last patch testing requests (4)
Created Duration User Patch Repo Result
2024/10/26 04:50 15m eadavis@qq.com patch upstream report log
2024/10/19 10:24 18m retest repro upstream report log
2024/10/19 10:24 13m retest repro upstream report log
2024/10/18 17:42 19m retest repro upstream report log

Sample crash report:
INFO: task bch-reclaim/loo:6361 blocked for more than 143 seconds.
      Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:bch-reclaim/loo state:D stack:14800 pid:6361  tgid:6361  ppid:2      task_flags:0x200040 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5377 [inline]
 __schedule+0x18bc/0x4c40 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 ksoftirqd/1/24:
 #0: ffff8880b873e7d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
1 lock held by khungtaskd/30:
 #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
4 locks held by kworker/u8:2/35:
 #0: ffff888029b9a948 ((wq_completion)btree_update){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff888029b9a948 ((wq_completion)btree_update){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc90000ab7c60 ((work_completion)(&c->btree_interior_update_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90000ab7c60 ((work_completion)(&c->btree_interior_update_work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #2: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #2: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: bch2_trans_srcu_lock+0x9a/0x1a0 fs/bcachefs/btree_iter.c:3202
 #3: ffff88805c8a66d0 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x682/0x14e0 fs/bcachefs/btree_update_interior.c:1180
5 locks held by kworker/u8:4/62:
2 locks held by getty/5587:
 #0: ffff888031aec0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002fde2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
6 locks held by syz-executor337/5846:
 #0: ffff8880327b20e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff8880327b20e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff8880327b20e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505
 #1: ffff88805c880278 (&c->state_lock){+.+.}-{4:4}, at: __bch2_fs_stop+0xfd/0x5c0 fs/bcachefs/super.c:622
 #2: ffff88805c8cb028 (&j->reclaim_lock){+.+.}-{4:4}, at: journal_flush_done+0x7b/0x400 fs/bcachefs/journal_reclaim.c:870
 #3: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #3: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #3: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x7e4/0xd30 fs/bcachefs/btree_iter.c:3377
 #4: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:164 [inline]
 #4: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:256 [inline]
 #4: ffff88805c884378 (&c->btree_trans_barrier){.+.+}-{0:0}, at: bch2_btree_key_cache_journal_flush+0x128/0xed0 fs/bcachefs/btree_key_cache.c:519
 #5: ffff88805c8a66d0 (&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/6361:
 #0: ffff88805c8cb028 (&j->reclaim_lock){+.+.}-{4:4}, at: bch2_journal_reclaim_thread+0x16d/0x570 fs/bcachefs/journal_reclaim.c:759
2 locks held by syz-executor337/8215:
1 lock held by syz-executor337/8216:
 #0: ffffffff8e93db80 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x530 kernel/rcu/tree.c:3741
3 locks held by syz-executor337/8232:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
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>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 8216 Comm: syz-executor337 Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:cpus_share_cache+0x0/0x120 kernel/sched/core.c:3903
Code: df e8 f4 fe d4 ff 49 39 c6 0f 94 c0 eb d7 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 55 41 57 41 56 41 54 53 b0 01 39 f7 0f 84 a1 00 00 00
RSP: 0018:ffffc90000a18918 EFLAGS: 00000097
RAX: 0000000000000001 RBX: 0000000000000000 RCX: dffffc0000000000
RDX: dffffc0000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000a18a50 R08: ffffffff942c3847 R09: 1ffffffff2858708
R10: dffffc0000000000 R11: fffffbfff2858709 R12: dffffc0000000000
R13: ffffffff8191de24 R14: 0000000000000001 R15: ffff88801cec8060
FS:  000055557a94c480(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1ad2bff000 CR3: 000000003287a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <IRQ>
 select_idle_sibling kernel/sched/fair.c:7857 [inline]
 select_task_rq_fair+0x1d0e/0x3b60 kernel/sched/fair.c:8603
 select_task_rq kernel/sched/core.c:3579 [inline]
 try_to_wake_up+0x65b/0x1470 kernel/sched/core.c:4314
 call_timer_fn+0x187/0x650 kernel/time/timer.c:1789
 expire_timers kernel/time/timer.c:1840 [inline]
 __run_timers kernel/time/timer.c:2414 [inline]
 __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2426
 run_timer_base kernel/time/timer.c:2435 [inline]
 run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2445
 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561
 __do_softirq kernel/softirq.c:595 [inline]
 invoke_softirq kernel/softirq.c:435 [inline]
 __irq_exit_rcu+0xf7/0x220 kernel/softirq.c:662
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:678
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1049
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:console_trylock_spinning kernel/printk/printk.c:2061 [inline]
RIP: 0010:vprintk_emit+0x700/0xa10 kernel/printk/printk.c:2431
Code: 00 e8 e4 d3 20 00 4c 8d bc 24 a0 00 00 00 4d 85 e4 75 07 e8 d2 d3 20 00 eb 06 e8 cb d3 20 00 fb 49 bc 00 00 00 00 00 fc ff df <48> c7 c7 80 43 81 8e 31 f6 ba 01 00 00 00 31 c9 41 b8 01 00 00 00
RSP: 0018:ffffc90003447780 EFLAGS: 00000293
RAX: ffffffff819e89f5 RBX: 0000000000000000 RCX: ffff888029d9da00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003447890 R08: ffffffff819e89ce R09: 1ffffffff20344ee
R10: dffffc0000000000 R11: fffffbfff20344ef R12: dffffc0000000000
R13: 1ffff92000688ef4 R14: ffffffff819e8830 R15: ffffc90003447820
 _printk+0xd5/0x120 kernel/printk/printk.c:2457
 bch2_fs_get_tree+0x100b/0x1740 fs/bcachefs/fs.c:2287
 vfs_get_tree+0x90/0x2b0 fs/super.c:1814
 do_new_mount+0x2be/0xb40 fs/namespace.c:3560
 do_mount fs/namespace.c:3900 [inline]
 __do_sys_mount fs/namespace.c:4111 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4088
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1adaa2686a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc208e2c08 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc208e2c60 RCX: 00007f1adaa2686a
RDX: 00002000000000c0 RSI: 0000200000000180 RDI: 00007ffc208e2c60
RBP: 0000200000000180 R08: 00007ffc208e2ca0 R09: 00000000000059d0
R10: 0000000000000010 R11: 0000000000000282 R12: 00002000000000c0
R13: 00007ffc208e2ca0 R14: 00000000000059d6 R15: 0000200000006200
 </TASK>

Crashes (1155):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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/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/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 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/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/02/14 12:34 upstream ab68d7eb7b1a d9a046cf .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/14 10:24 upstream ab68d7eb7b1a d9a046cf .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/14 10:03 upstream ab68d7eb7b1a d9a046cf .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/14 03:19 upstream ab68d7eb7b1a d9a046cf .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/14 01:11 upstream ab68d7eb7b1a a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 23:46 upstream ab68d7eb7b1a a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 22:14 upstream ab68d7eb7b1a a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 19:57 upstream ab68d7eb7b1a a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 15:54 upstream 4dc1d1bec898 a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 14:51 upstream 4dc1d1bec898 a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 13:19 upstream 4dc1d1bec898 a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 11:06 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 09:43 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 07:47 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 04:17 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 02:25 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 00:47 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/13 00:28 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 21:46 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 20:34 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 18:37 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 16:49 upstream 09fbf3d50205 b27c2402 .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/12 15:15 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 12:29 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 10:15 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 08:57 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 07:17 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 05:46 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 04:34 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/12 00:08 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 23:23 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 21:39 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 20:20 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 18:33 upstream febbc555cf0f f2baddf5 .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/11 15:11 upstream febbc555cf0f f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 12:41 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 11:12 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 10:00 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 08:33 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 06:35 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 03:49 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/11 01:10 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in bch2_journal_reclaim_thread
2025/02/10 22:58 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root 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/11 14:09 linux-next df5d6180169a f2baddf5 .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/11 05:15 linux-next df5d6180169a 43f51a00 .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/15 19:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a64dcfb451e2 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in bch2_journal_reclaim_thread
2025/02/10 20:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 43f51a00 .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.