syzbot


INFO: task hung in __closure_sync

Status: upstream: reported C repro on 2024/05/03 17:32
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+7bf808f7fe4a6549f36e@syzkaller.appspotmail.com
First crash: 443d, last: 3h04m
Cause bisection: introduced by (bisect log) :
commit 03ef80b469d5d83530ce1ce15be78a40e5300f9b
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Sep 23 22:41:51 2023 +0000

  bcachefs: Ignore unknown mount options

Crash: INFO: task hung in __closure_sync (log)
Repro: C syz .config
  
Discussions (14)
Title Replies (including bot) Last reply
[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] Monthly bcachefs report (Oct 2024) 0 (1) 2024/10/14 19:38
[syzbot] Monthly bcachefs report (Sep 2024) 0 (1) 2024/09/13 10:03
[syzbot] Monthly bcachefs report (Aug 2024) 0 (1) 2024/08/13 08:53
[syzbot] Monthly bcachefs report (Jul 2024) 0 (1) 2024/07/12 12:53
[syzbot] Monthly bcachefs report (Jun 2024) 0 (1) 2024/06/11 08:27
[syzbot] [bcachefs?] INFO: task hung in __closure_sync 0 (2) 2024/05/04 00:29
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/10/18 18:10 34m retest repro upstream report log
2024/10/18 15:52 17m retest repro upstream report log
2024/10/18 15:52 17m retest repro upstream report log
2024/10/18 15:52 18m retest repro upstream report log
2024/10/18 15:52 17m retest repro upstream report log
2024/10/18 15:52 17m retest repro upstream report log
2024/09/01 02:57 23m retest repro upstream OK log
2024/09/01 00:00 19m retest repro upstream OK log
2024/09/01 00:00 11m retest repro upstream report log
2024/09/01 00:00 12m retest repro upstream report log

Sample crash report:
INFO: task kworker/u8:3:49 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u8:3    state:D stack:23336 pid:49    tgid:49    ppid:2      task_flags:0x4208060 flags:0x00004000
Workqueue: btree_node_rewrite async_btree_node_rewrite_work
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5401 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6790
 __schedule_loop kernel/sched/core.c:6868 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6883
 __closure_sync+0x163/0x220 lib/closure.c:146
 bch2_wait_on_allocator fs/bcachefs/alloc_foreground.h:315 [inline]
 bch2_btree_update_start+0x18dc/0x1de0 fs/bcachefs/btree_update_interior.c:1293
 bch2_btree_node_rewrite+0x17e/0x1120 fs/bcachefs/btree_update_interior.c:2246
 bch2_btree_node_rewrite_key+0x273/0x320 fs/bcachefs/btree_update_interior.c:2312
 async_btree_node_rewrite_work+0x110/0x4f0 fs/bcachefs/btree_update_interior.c:2369
 process_one_work kernel/workqueue.c:3238 [inline]
 process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3321
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
INFO: task syz-executor836:5860 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor836 state:D stack:19432 pid:5860  tgid:5860  ppid:5859   task_flags:0x400140 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5401 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6790
 __schedule_loop kernel/sched/core.c:6868 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6883
 __closure_sync+0x163/0x220 lib/closure.c:146
 bch2_wait_on_allocator fs/bcachefs/alloc_foreground.h:315 [inline]
 bch2_btree_update_start+0x18dc/0x1de0 fs/bcachefs/btree_update_interior.c:1293
 bch2_btree_split_leaf+0x14b/0x8e0 fs/bcachefs/btree_update_interior.c:1921
 bch2_trans_commit_error+0x1b7/0x1130 fs/bcachefs/btree_trans_commit.c:914
 __bch2_trans_commit+0x1bb5/0x8870 fs/bcachefs/btree_trans_commit.c:1104
 bch2_trans_commit fs/bcachefs/btree_update.h:241 [inline]
 bch2_journal_replay+0x1e85/0x2630 fs/bcachefs/recovery.c:429
 bch2_run_recovery_pass fs/bcachefs/recovery_passes.c:484 [inline]
 __bch2_run_recovery_passes+0x395/0x1010 fs/bcachefs/recovery_passes.c:539
 bch2_run_recovery_passes+0x184/0x210 fs/bcachefs/recovery_passes.c:610
 bch2_fs_recovery+0x2690/0x3a50 fs/bcachefs/recovery.c:1005
 bch2_fs_start+0xaaf/0xda0 fs/bcachefs/super.c:1213
 bch2_fs_get_tree+0xb39/0x1520 fs/bcachefs/fs.c:2488
 vfs_get_tree+0x92/0x2b0 fs/super.c:1804
 do_new_mount+0x24a/0xa40 fs/namespace.c:3902
 do_mount fs/namespace.c:4239 [inline]
 __do_sys_mount fs/namespace.c:4450 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4427
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0de765de2a
RSP: 002b:00007fff5b01a138 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fff5b01a150 RCX: 00007f0de765de2a
RDX: 00002000000000c0 RSI: 0000200000000040 RDI: 00007fff5b01a150
RBP: 0000200000000040 R08: 00007fff5b01a190 R09: 00000000000058fe
R10: 0000000000808040 R11: 0000000000000282 R12: 00002000000000c0
R13: 00007fff5b01a190 R14: 0000000000000003 R15: 0000000000808040
 </TASK>
INFO: task bch-reclaim/loo:5869 blocked for more than 144 seconds.
      Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:bch-reclaim/loo state:D stack:23944 pid:5869  tgid:5869  ppid:2      task_flags:0x200840 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5401 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6790
 __schedule_loop kernel/sched/core.c:6868 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6883
 __closure_sync+0x163/0x220 lib/closure.c:146
 bch2_wait_on_allocator fs/bcachefs/alloc_foreground.h:315 [inline]
 bch2_btree_update_start+0x18dc/0x1de0 fs/bcachefs/btree_update_interior.c:1293
 bch2_btree_split_leaf+0x14b/0x8e0 fs/bcachefs/btree_update_interior.c:1921
 bch2_trans_commit_error+0x1b7/0x1130 fs/bcachefs/btree_trans_commit.c:914
 __bch2_trans_commit+0x1bb5/0x8870 fs/bcachefs/btree_trans_commit.c:1104
 bch2_trans_commit fs/bcachefs/btree_update.h:241 [inline]
 bch2_btree_write_buffer_flush_locked+0x451f/0x4dd0 fs/bcachefs/btree_write_buffer.c:454
 btree_write_buffer_flush_seq+0x18c7/0x1a40 fs/bcachefs/btree_write_buffer.c:572
 bch2_btree_write_buffer_journal_flush+0x69/0xb0 fs/bcachefs/btree_write_buffer.c:588
 journal_flush_pins+0x8e3/0xe90 fs/bcachefs/journal_reclaim.c:598
 __bch2_journal_reclaim+0x8e9/0xea0 fs/bcachefs/journal_reclaim.c:726
 bch2_journal_reclaim_thread+0x177/0x4f0 fs/bcachefs/journal_reclaim.c:768
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13f160 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13f160 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13f160 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
4 locks held by kworker/u8:3/49:
 #0: ffff8880335fc948 ((wq_completion)btree_node_rewrite){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline]
 #0: ffff8880335fc948 ((wq_completion)btree_node_rewrite){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3321
 #1: ffffc90000b97bc0 ((work_completion)(&a->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline]
 #1: ffffc90000b97bc0 ((work_completion)(&a->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3321
 #2: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:161 [inline]
 #2: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:253 [inline]
 #2: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: bch2_trans_srcu_lock+0xaf/0x220 fs/bcachefs/btree_iter.c:3299
 #3: ffff888072b26710 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x542/0x1de0 fs/bcachefs/btree_update_interior.c:1211
5 locks held by kworker/u8:6/1335:
2 locks held by getty/5596:
 #0: ffff88814d8500a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000333b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
2 locks held by syz-executor836/5860:
 #0: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:161 [inline]
 #0: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:253 [inline]
 #0: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: bch2_trans_srcu_lock+0xaf/0x220 fs/bcachefs/btree_iter.c:3299
 #1: ffff888072b26710 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x542/0x1de0 fs/bcachefs/btree_update_interior.c:1211
4 locks held by bch-reclaim/loo/5869:
 #0: ffff888072b4af68 (&j->reclaim_lock){+.+.}-{4:4}, at: bch2_journal_reclaim_thread+0x16b/0x4f0 fs/bcachefs/journal_reclaim.c:767
 #1: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:161 [inline]
 #1: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:253 [inline]
 #1: ffff888072b04398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x7f4/0xd80 fs/bcachefs/btree_iter.c:3505
 #2: ffff888072b04740 (&wb->flushing.lock){+.+.}-{4:4}, at: btree_write_buffer_flush_seq+0x18bd/0x1a40 fs/bcachefs/btree_write_buffer.c:571
 #3: ffff888072b26710 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x542/0x1de0 fs/bcachefs/btree_update_interior.c:1211

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:307 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:470
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:pv_native_safe_halt+0x13/0x20 arch/x86/kernel/paravirt.c:82
Code: cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 93 fd 1f 00 f3 0f 1e fa fb f4 <e9> 88 dd 02 00 cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90000197de0 EFLAGS: 000002c6
RAX: a287eeebbbd4ed00 RBX: ffffffff81976b68 RCX: a287eeebbbd4ed00
RDX: 0000000000000001 RSI: ffffffff8d98552e RDI: ffffffff8be1ca80
RBP: ffffc90000197f20 R08: ffff8880b8732f5b R09: 1ffff110170e65eb
R10: dffffc0000000000 R11: ffffed10170e65ec R12: ffffffff8fa0cbf0
R13: 0000000000000001 R14: 0000000000000001 R15: 1ffff11003ad4b40
FS:  0000000000000000(0000) GS:ffff888125d4f000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ee2a7ca660 CR3: 000000000df38000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 arch_safe_halt arch/x86/include/asm/paravirt.h:107 [inline]
 default_idle+0x13/0x20 arch/x86/kernel/process.c:749
 default_idle_call+0x74/0xb0 kernel/sched/idle.c:117
 cpuidle_idle_call kernel/sched/idle.c:185 [inline]
 do_idle+0x1e8/0x510 kernel/sched/idle.c:325
 cpu_startup_entry+0x44/0x60 kernel/sched/idle.c:423
 start_secondary+0x101/0x110 arch/x86/kernel/smpboot.c:315
 common_startup_64+0x13e/0x147
 </TASK>

Crashes (8125):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/12 20:08 upstream 379f604cc3dc 3cda49cf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/06 10:08 upstream 05df91921da6 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/22 13:56 upstream d608703fcdd9 0919b50b .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/16 04:11 upstream 088d13246a46 cfde8269 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/11 03:24 upstream bec6f00f120e 77908e5f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/10 09:25 upstream 0e1329d4045c 77908e5f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/10 01:06 upstream 9c69f8884904 77908e5f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/05/02 02:45 upstream 4f79eaa2ceac 51b137cd .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/29 16:15 upstream ca91b9500108 aeb6ec69 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/28 09:28 upstream b4432656b36e c6b4fb39 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/27 21:52 upstream 5bc1018675ec c6b4fb39 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/27 12:12 upstream 5bc1018675ec c6b4fb39 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/27 07:12 upstream 5bc1018675ec c6b4fb39 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/24 02:05 upstream a79be02bba5c 73a168d0 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/23 09:59 upstream bc3372351d0c 53a8b9bd .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/22 12:11 upstream a33b5a08cbbd 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/20 15:24 upstream 119009db2674 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/20 14:54 upstream 119009db2674 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/04/18 08:53 upstream b5c6891b2c5b 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/03/27 11:07 upstream 1e1ba8d23dae 20510e88 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/03/23 09:57 upstream 183601b78a9b 4e8d3850 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/03/22 15:43 upstream 88d324e69ea9 c6512ef7 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/03/16 19:41 upstream 31d7109a19f6 e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/21 07:30 upstream 100ceb4817a2 6e87cfa2 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/17 01:11 upstream ce69b4019001 f9e07a6e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/16 08:16 upstream 619f0b6fad52 968edaf4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/16 00:36 upstream 619f0b6fad52 968edaf4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/09/23 06:21 upstream af9c191ac2a0 6f888b75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/09/20 16:53 upstream 2004cef11ea0 6f888b75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/09/20 15:56 upstream 2004cef11ea0 6f888b75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/09/20 04:45 upstream 2a17bb8c204f 6f888b75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/09/20 03:21 upstream 2a17bb8c204f 6f888b75 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/09/18 01:56 upstream fc1dc0d50780 c673ca06 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/05/14 04:42 upstream 8815da98e06a fdb4c10c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/09 07:15 upstream 6d7ddd805123 20bf80e1 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/09 03:28 upstream 6d7ddd805123 20bf80e1 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/09 02:53 upstream 6d7ddd805123 20bf80e1 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/08 10:42 upstream dccb07f2914c 4cf3f9b3 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/13 03:05 upstream 3f31a806a62e 3cda49cf .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 __closure_sync
2025/07/08 20:21 upstream d006330be3f7 4d9fdfa4 .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 __closure_sync
2025/06/23 03:03 upstream b67ec639010f d6cdfb8a .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 __closure_sync
2025/06/22 15:33 upstream 739a6c93cc75 d6cdfb8a .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 __closure_sync
2025/05/25 04:47 upstream b1427432d3b6 ed351ea7 .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 __closure_sync
2025/05/22 16:26 upstream d608703fcdd9 0919b50b .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 __closure_sync
2025/05/20 03:01 upstream a5806cd506af b84f0537 .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 __closure_sync
2025/05/19 01:42 upstream a5806cd506af f41472b0 .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 __closure_sync
2025/05/17 05:00 upstream 3c21441eeffc cfde8269 .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 __closure_sync
2025/05/05 18:07 upstream 92a09c47464d 6ca47dd8 .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 __closure_sync
2025/05/02 17:59 upstream ebd297a2affa d7f099d1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in __closure_sync
2025/05/02 16:48 upstream ebd297a2affa d7f099d1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in __closure_sync
2025/05/02 15:19 upstream ebd297a2affa d7f099d1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in __closure_sync
2025/05/02 06:10 upstream ebd297a2affa 51b137cd .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 __closure_sync
2024/08/16 07:45 upstream d7a5aa4b3c00 e4bacdaf .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 __closure_sync
2024/07/16 04:33 upstream 5e0497553643 e8709b21 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/07/13 23:14 upstream 528dd46d0fc3 eaeb5c15 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/07/13 22:05 upstream 528dd46d0fc3 eaeb5c15 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/07/06 19:12 upstream 1dd28064d416 2a40360c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/06/11 09:57 upstream 83a7eefedc9b b7d9eb04 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/06/08 18:07 upstream dc772f8237f9 82c05ab8 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/06/06 14:21 upstream 2df0193e62cf 121701b6 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/23 21:51 upstream b6394d6f7159 4c2072ee .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/23 12:06 upstream 8f6a15f095a6 4d098039 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/05/07 04:12 upstream dccb07f2914c fa7a5cf0 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/05 05:58 upstream 7367539ad4b0 610f2a54 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/05/03 17:32 upstream f03359bca01b dd26401e .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __closure_sync
2024/08/17 18:13 upstream e5fa841af679 e1c76ab2 .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 __closure_sync
2024/08/17 14:26 upstream e5fa841af679 e1c76ab2 .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 __closure_sync
2024/08/17 05:39 upstream 670c12ce09a8 e1c76ab2 .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 __closure_sync
2024/08/17 03:17 upstream 670c12ce09a8 e1c76ab2 .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 __closure_sync
2024/08/17 00:49 upstream 670c12ce09a8 e1c76ab2 .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 __closure_sync
2025/07/20 10:47 upstream bf61759db409 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/20 09:40 upstream bf61759db409 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/20 04:52 upstream bf61759db409 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 20:54 upstream 4871b7cb27f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 19:03 upstream 4871b7cb27f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 08:43 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 05:02 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 03:03 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 00:08 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 22:52 upstream d786aba32000 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 10:34 upstream 6832a9317eee 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 09:21 upstream 6832a9317eee 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 08:10 upstream 6832a9317eee 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 04:20 upstream 6832a9317eee 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 01:15 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/18 01:13 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 21:06 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 15:01 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 06:14 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 05:10 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 02:36 upstream e2291551827f 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/17 00:02 upstream 155a3c003e55 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 21:55 upstream 155a3c003e55 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 14:14 upstream 155a3c003e55 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 08:37 upstream 155a3c003e55 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 03:28 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 02:21 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/16 00:33 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/15 22:29 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/15 18:45 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/15 17:08 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/15 14:28 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/15 01:01 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 23:22 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 20:48 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 18:45 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 17:38 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 12:46 upstream 347e9f5043c8 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 10:15 upstream 347e9f5043c8 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 06:06 upstream 5d5d62298b8b 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 03:13 upstream 5d5d62298b8b 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/14 00:57 upstream 5d5d62298b8b 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/13 19:45 upstream 5d5d62298b8b 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/13 10:27 upstream 3f31a806a62e 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/08 21:38 upstream d006330be3f7 abade794 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2024/06/24 12:52 upstream f2661062f16b edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __closure_sync
2024/06/19 19:38 upstream 2ccbdf43d5e7 41b7e219 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __closure_sync
2024/05/03 13:46 upstream f03359bca01b dd26401e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/07/19 20:45 linux-next d086c886ceb9 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/07/13 08:45 linux-next a62b7a37e6fc 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/07/17 09:05 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ec4801305969 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __closure_sync
* Struck through repros no longer work on HEAD.