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: 288d, last: 1d01h
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 (9)
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] 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 syz-executor405:5820 blocked for more than 143 seconds.
      Not tainted 6.13.0-syzkaller-00164-g100ceb4817a2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor405 state:D stack:18040 pid:5820  tgid:5820  ppid:5818   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5369 [inline]
 __schedule+0x17fb/0x4be0 kernel/sched/core.c:6756
 __schedule_loop kernel/sched/core.c:6833 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6848
 __closure_sync+0x259/0x2f0 lib/closure.c:146
 bch2_wait_on_allocator fs/bcachefs/alloc_foreground.h:239 [inline]
 bch2_btree_update_start+0x11a2/0x14e0 fs/bcachefs/btree_update_interior.c:1269
 bch2_btree_split_leaf+0x123/0x840 fs/bcachefs/btree_update_interior.c:1856
 bch2_trans_commit_error+0x212/0x1380 fs/bcachefs/btree_trans_commit.c:942
 __bch2_trans_commit+0x7ead/0x93c0 fs/bcachefs/btree_trans_commit.c:1140
 bch2_trans_commit fs/bcachefs/btree_update.h:184 [inline]
 bch2_logged_op_start+0x1c8/0x310 fs/bcachefs/logged_ops.c:92
 bch2_truncate+0x19e/0x2d0 fs/bcachefs/io_misc.c:294
 bchfs_truncate+0x85f/0xc90 fs/bcachefs/fs-io.c:464
 notify_change+0xbca/0xe90 fs/attr.c:552
 do_truncate+0x220/0x310 fs/open.c:65
 handle_truncate fs/namei.c:3449 [inline]
 do_open fs/namei.c:3832 [inline]
 path_openat+0x2e1e/0x3590 fs/namei.c:3987
 do_filp_open+0x27f/0x4e0 fs/namei.c:4014
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1395
 do_sys_open fs/open.c:1410 [inline]
 __do_sys_openat fs/open.c:1426 [inline]
 __se_sys_openat fs/open.c:1421 [inline]
 __x64_sys_openat+0x247/0x2a0 fs/open.c:1421
 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:0x7fd5038c0d99
RSP: 002b:00007fff8ff95fb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fd50390a095 RCX: 00007fd5038c0d99
RDX: 0000000000008243 RSI: 0000000020000100 RDI: 00000000ffffff9c
RBP: 00007fd50393a5f0 R08: 0000000000005901 R09: 000055555c9524c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff8ff95fe0
R13: 00007fff8ff96208 R14: 431bde82d7b634db R15: 00007fd50390a03b
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6744
1 lock held by klogd/5183:
 #0: ffff8880b863e798 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
2 locks held by getty/5581:
 #0: ffff88814cfc70a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
5 locks held by syz-executor405/5820:
 #0: ffff88807fb3e420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:547
 #1: ffff8880714d0148 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:831 [inline]
 #1: ffff8880714d0148 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: do_truncate+0x20c/0x310 fs/open.c:63
 #2: ffff888075300a38 (&c->snapshot_create_lock){.+.+}-{4:4}, at: bch2_truncate+0x166/0x2d0 fs/bcachefs/io_misc.c:292
 #3: ffff888075304398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:158 [inline]
 #3: ffff888075304398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:249 [inline]
 #3: ffff888075304398 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x7e1/0xd30 fs/bcachefs/btree_iter.c:3228
 #4: ffff8880753266d0 (&c->gc_lock){.+.+}-{4:4}, at: bch2_btree_update_start+0x682/0x14e0 fs/bcachefs/btree_update_interior.c:1197

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.13.0-syzkaller-00164-g100ceb4817a2 #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:234 [inline]
 watchdog+0xff6/0x1040 kernel/hung_task.c:397
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-syzkaller-00164-g100ceb4817a2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:rcu_is_watching+0x70/0xb0 kernel/rcu/tree.c:739
Code: c3 d8 7c 03 00 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 84 c0 75 22 8b 03 65 ff 0d b1 ce 7e 7e 74 10 83 e0 04 c1 e8 02 5b <41> 5e 41 5f c3 cc cc cc cc e8 a2 41 85 ff eb e9 89 d9 80 e1 07 80
RSP: 0018:ffffc90000bc75c8 EFLAGS: 00000202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff817acd60
RDX: 0000000000000000 RSI: ffffffff8c5f27c0 RDI: ffffffff8c5f2780
RBP: ffffc90000bc7720 R08: ffffffff9018d4f7 R09: 1ffffffff2031a9e
R10: dffffc0000000000 R11: fffffbfff2031a9f R12: 1ffff92000178ec8
R13: ffffffff813f9a9b R14: ffffffff8e2deb50 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b6bcfcd600 CR3: 000000000e736000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 trace_lock_release include/trace/events/lock.h:69 [inline]
 lock_release+0xbf/0xa30 kernel/locking/lockdep.c:5860
 __raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
 _raw_spin_unlock+0x16/0x50 kernel/locking/spinlock.c:186
 spin_unlock include/linux/spinlock.h:391 [inline]
 __text_poke+0xa6b/0xd30 arch/x86/kernel/alternative.c:1989
 text_poke arch/x86/kernel/alternative.c:2013 [inline]
 text_poke_bp_batch+0x8cd/0xb30 arch/x86/kernel/alternative.c:2402
 text_poke_flush arch/x86/kernel/alternative.c:2515 [inline]
 text_poke_finish+0x30/0x50 arch/x86/kernel/alternative.c:2522
 arch_jump_label_transform_apply+0x1c/0x30 arch/x86/kernel/jump_label.c:146
 static_key_disable_cpuslocked+0xd2/0x1c0 kernel/jump_label.c:240
 static_key_disable+0x1a/0x20 kernel/jump_label.c:248
 toggle_allocation_gate+0x1bf/0x260 mm/kfence/core.c:854
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317
 worker_thread+0x870/0xd30 kernel/workqueue.c:3398
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.595 msecs

Crashes (7249):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2025/01/14 07:06 upstream c45323b7560e b1f1cd88 .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/13 23:19 upstream 5bc55a333a2f 249ceea9 .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/12 03:06 upstream b62cef9a5c67 6dbc6a9b .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/11 18:10 upstream 77a903cd8e5a 6dbc6a9b .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/11 12:48 upstream 77a903cd8e5a 6dbc6a9b .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/09 21:17 upstream eea6e4b4dfb8 9220929f .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/09 18:19 upstream eea6e4b4dfb8 9220929f .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/09 04:38 upstream 0b7958fa05d5 f3558dbf .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/06 00:06 upstream ab75170520d4 f3558dbf .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/05 19:05 upstream ab75170520d4 f3558dbf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/05 16:23 upstream ab75170520d4 f3558dbf .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/05 09:46 upstream ab75170520d4 f3558dbf .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/05 08:53 upstream ab75170520d4 f3558dbf .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/02 14:28 upstream 56e6a3499e14 d3ccff63 .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
2025/01/02 09:26 upstream 56e6a3499e14 d3ccff63 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs INFO: task hung in __closure_sync
2025/01/01 08:41 upstream ccb98ccef0e5 d3ccff63 .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/01 06:45 upstream ccb98ccef0e5 d3ccff63 .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/12/31 23:26 upstream ccb98ccef0e5 d3ccff63 .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/12/31 17:52 upstream ccb98ccef0e5 d3ccff63 .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/12/31 12:52 upstream ccb98ccef0e5 d3ccff63 .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/12/30 19:19 upstream fc033cf25e61 d3ccff63 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs INFO: task hung in __closure_sync
2024/12/30 02:00 upstream 4099a71718b0 d3ccff63 .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/12/28 20:07 upstream fd0584d220fe d3ccff63 .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/12/27 18:14 upstream d6ef8b40d075 d3ccff63 .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/12/27 16:54 upstream d6ef8b40d075 d3ccff63 .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/12/27 15:39 upstream d6ef8b40d075 d3ccff63 .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/12/27 14:49 upstream d6ef8b40d075 d3ccff63 .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/12/27 06:04 upstream d6ef8b40d075 d3ccff63 .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/12/25 05:34 upstream 9b2ffa6148b1 444551c4 .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/12/24 12:22 upstream f07044dd0df0 444551c4 .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/12/24 02:09 upstream f07044dd0df0 444551c4 .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/12/22 09:16 upstream a99b4a369a54 d7f584ee .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/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
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
2025/01/06 08:05 linux-next 8155b4ef3466 f3558dbf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/01/04 18:34 linux-next 8155b4ef3466 f3558dbf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/01/03 02:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __closure_sync
2025/01/03 10:03 upstream 0bc21e701a6f d3ccff63 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs 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/02/14 17:04 upstream 128c8f96eb86 d9a046cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2025/02/13 22:10 upstream ab68d7eb7b1a d9a046cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2025/02/13 19:51 upstream ab68d7eb7b1a a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/13 18:00 upstream 4dc1d1bec898 a98a8417 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
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 __closure_sync
2025/02/13 09:29 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/13 08:25 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/13 07:19 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/13 06:29 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/13 04:26 upstream 4dc1d1bec898 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/12 17:20 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/12 15:53 upstream 09fbf3d50205 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/12 10:00 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/12 06:32 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 17:43 upstream febbc555cf0f f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 15:47 upstream febbc555cf0f f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 13:37 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2025/02/11 10:48 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 06:18 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 04:14 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 01:43 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/11 00:16 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 21:00 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 19:51 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 15:48 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 14:23 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 12:35 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __closure_sync
2025/02/10 10:39 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 10:19 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/10 06:21 upstream 69b54314c975 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/09 23:06 upstream 69b54314c975 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/09 18:57 upstream 9946eaf552b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/08 10:42 upstream 7ee983c850b4 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/08 08:35 upstream 7ee983c850b4 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/07 15:36 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/07 11:06 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/07 09:52 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 23:49 upstream 92514ef226f5 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 22:12 upstream 92514ef226f5 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 19:06 upstream 92514ef226f5 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 09:01 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 06:23 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 04:46 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/06 01:43 upstream 5c8c229261f1 4dc70884 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/05 21:25 upstream 5c8c229261f1 4dc70884 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __closure_sync
2025/02/05 20:03 upstream 5c8c229261f1 4dc70884 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs 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/02/12 12:04 linux-next c674aa7c289e f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/02/11 11:53 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 __closure_sync
2025/02/10 00:09 linux-next ed58d103e6da ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/02/08 15:51 linux-next ed58d103e6da ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __closure_sync
2025/02/08 11:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __closure_sync
2025/02/07 01:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 53657d1b .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.