syzbot


INFO: task hung in sb_start_write (2)

Status: upstream: reported on 2025/05/23 04:46
Subsystems: kernfs
[Documentation on labels]
Reported-by: syzbot+b3fba2e269970207b61d@syzkaller.appspotmail.com
First crash: 454d, last: 1d09h
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly kernfs report (Aug 2025) 0 (1) 2025/08/23 16:32
[syzbot] Monthly f2fs report (Aug 2025) 0 (1) 2025/08/01 13:49
[syzbot] Monthly f2fs report (Jul 2025) 0 (1) 2025/07/01 09:24
[syzbot] [jfs?] [xfs?] [bcachefs?] INFO: task hung in sb_start_write (2) 0 (1) 2025/05/23 04:46
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in sb_start_write ext4 xfs 1 516 583d 661d 0/29 auto-obsoleted due to no activity on 2024/12/19 19:32
linux-6.1 INFO: task hung in sb_start_write 1 4 657d 668d 0/3 auto-obsoleted due to no activity on 2024/11/05 17:25
linux-5.15 INFO: task hung in sb_start_write 1 2 616d 660d 0/3 auto-obsoleted due to no activity on 2024/12/17 04:15

Sample crash report:
INFO: task syz.0.589:8745 blocked for more than 143 seconds.
      Not tainted syzkaller #0
task:syz.0.589       state:D stack:26000 pid:8745  tgid:8740  ppid:5601   task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16ec/0x5620 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 percpu_rwsem_wait+0x317/0x480 kernel/locking/percpu-rwsem.c:164
 __percpu_down_read+0xfc/0x140 kernel/locking/percpu-rwsem.c:180
 percpu_down_read_internal include/linux/percpu-rwsem.h:67 [inline]
 percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 __sb_start_write include/linux/fs/super.h:19 [inline]
 sb_start_write+0x18e/0x1c0 include/linux/fs/super.h:125
 mnt_want_write+0x41/0x90 fs/namespace.c:493
 open_last_lookups fs/namei.c:4600 [inline]
 path_openat+0xaec/0x38a0 fs/namei.c:4855
 do_file_open+0x23e/0x4a0 fs/namei.c:4887
 do_sys_openat2+0x113/0x200 fs/open.c:1364
 do_sys_open fs/open.c:1370 [inline]
 __do_sys_openat fs/open.c:1386 [inline]
 __se_sys_openat fs/open.c:1381 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1381
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fee94ccce59
RSP: 002b:00007fee92efd028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fee94f46090 RCX: 00007fee94ccce59
RDX: 000000000000275a RSI: 0000200000000080 RDI: ffffffffffffff9c
RBP: 00007fee94d62d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fee94f46128 R14: 00007fee94f46090 R15: 00007ffcd0e6e528
 </TASK>
INFO: task syz.0.589:8746 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.589       state:D stack:24664 pid:8746  tgid:8740  ppid:5601   task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16ec/0x5620 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 percpu_rwsem_wait+0x317/0x480 kernel/locking/percpu-rwsem.c:164
 __percpu_down_read+0xfc/0x140 kernel/locking/percpu-rwsem.c:180
 percpu_down_read_internal include/linux/percpu-rwsem.h:67 [inline]
 percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 __sb_start_write include/linux/fs/super.h:19 [inline]
 sb_start_write+0x18e/0x1c0 include/linux/fs/super.h:125
 mnt_want_write+0x41/0x90 fs/namespace.c:493
 open_last_lookups fs/namei.c:4600 [inline]
 path_openat+0xaec/0x38a0 fs/namei.c:4855
 do_file_open+0x23e/0x4a0 fs/namei.c:4887
 do_sys_openat2+0x113/0x200 fs/open.c:1364
 do_sys_open fs/open.c:1370 [inline]
 __do_sys_openat fs/open.c:1386 [inline]
 __se_sys_openat fs/open.c:1381 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1381
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fee94ccce59
RSP: 002b:00007fee92edc028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fee94f46180 RCX: 00007fee94ccce59
RDX: 00000000000c4042 RSI: 0000200000000300 RDI: ffffffffffffff9c
RBP: 00007fee94d62d6f R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000001ff R11: 0000000000000246 R12: 0000000000000000
R13: 00007fee94f46218 R14: 00007fee94f46180 R15: 00007ffcd0e6e528
 </TASK>

Showing all locks held in the system:
4 locks held by pr/legacy/17:
1 lock held by khungtaskd/38:
 #0: ffffffff8dfc81c0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8dfc81c0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8dfc81c0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/u8:6/162:
 #0: ffff888032e7c938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888032e7c938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc9000153fc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000153fc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x124/0x1680 net/ipv6/addrconf.c:4206
3 locks held by kworker/u8:7/168:
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc9000392fc40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000392fc40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: linkwatch_event+0xe/0x60 net/core/link_watch.c:313
2 locks held by kworker/u8:13/3386:
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc9000e2bfc40 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000e2bfc40 ((reaper_work).work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
2 locks held by kworker/u8:15/3525:
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc9000e84fc40 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000e84fc40 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
1 lock held by dhcpcd/5262:
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_delroute+0x130/0x330 net/ipv4/fib_frontend.c:888
2 locks held by getty/5352:
 #0: ffff88823bf7e0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003cc62e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13a0 drivers/tty/n_tty.c:2211
5 locks held by kworker/u8:23/6196:
 #0: ffff88801b290938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801b290938 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc900070e7c40 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc900070e7c40 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f348d60 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf4/0x800 net/core/net_namespace.c:673
 #3: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: ops_exit_rtnl_list net/core/net_namespace.c:173 [inline]
 #3: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: ops_undo_list+0x2a4/0x940 net/core/net_namespace.c:248
 #4: ffffffff8dfce370 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
1 lock held by syz.0.589/8745:
 #0: ffff88805f2b0480 (sb_writers#18){++++}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
1 lock held by syz.0.589/8746:
 #0: ffff88805f2b0480 (sb_writers#18){++++}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
3 locks held by kworker/0:7/9207:
3 locks held by kworker/1:7/9241:
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90005c9fc40 (deferred_process_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005c9fc40 (deferred_process_work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:104
3 locks held by kworker/1:8/9324:
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90006167c40 (rx_mode_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90006167c40 (rx_mode_work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: netdev_rx_mode_work+0x1c/0x450 net/core/dev_addr_lists.c:1312
1 lock held by syz-executor/9920:
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: inet6_rtm_newaddr+0x65f/0xe30 net/ipv6/addrconf.c:5039
1 lock held by syz-executor/9997:
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: inet6_rtm_newaddr+0x65f/0xe30 net/ipv6/addrconf.c:5039
2 locks held by udevd/10224:
7 locks held by syz-executor/10238:
 #0: ffff888038518480 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2724 [inline]
 #0: ffff888038518480 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x22d/0xba0 fs/read_write.c:684
 #1: ffff888025c96078 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
 #2: ffff88802a0d7d28 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff88802a0d7d28 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x540 fs/kernfs/file.c:344
 #3: ffffffff8ebcfa98 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: new_device_store+0x13c/0x710 drivers/net/netdevsim/bus.c:184
 #4: ffff88806375c160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline]
 #4: ffff88806375c160 (&dev->mutex){....}-{4:4}, at: __device_attach+0x88/0x450 drivers/base/dd.c:1076
 #5: ffff88806b4fa310 (&devlink->lock_key#19){+.+.}-{4:4}, at: nsim_drv_probe+0xc9/0xc30 drivers/net/netdevsim/dev.c:1658
 #6: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #6: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_dev_lock+0x257/0x2f0 net/core/dev.c:2162
2 locks held by syz-executor/10451:
 #0: ffffffff8f891ac8 (&ops->srcu#2){.+.+}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8f891ac8 (&ops->srcu#2){.+.+}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8f891ac8 (&ops->srcu#2){.+.+}-{0:0}, at: rtnl_link_ops_get+0x23/0x250 net/core/rtnetlink.c:570
 #1: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #1: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline]
 #1: ffffffff8f357ab8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x883/0x1bb0 net/core/rtnetlink.c:4109

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 38 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline]
 watchdog+0xfd3/0x1030 kernel/hung_task.c:561
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 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: 17 Comm: pr/legacy Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:delay_tsc+0x5b/0xc0 arch/x86/lib/delay.c:79
Code: 90 49 89 d7 49 c1 e7 20 49 09 c7 4d 29 f7 49 39 df 73 53 bf 01 00 00 00 e8 02 e6 77 f6 65 8b 05 0b 18 4f 07 85 c0 74 1c f3 90 <bf> 01 00 00 00 e8 4b e4 77 f6 e8 46 78 01 00 39 c5 75 0e 0f 01 f9
RSP: 0018:ffffc900001679d0 EFLAGS: 00000286
RAX: 0000000080000000 RBX: 0000000000000899 RCX: 0000000000000000
RDX: 0000000000000113 RSI: ffffffff8ba75040 RDI: 00000000ffffffff
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffffff8b1ba7d0 R12: 1ffffffff336392e
R13: 00000000ffffffff R14: 000001132d62e7b4 R15: 000000000000011a
FS:  0000000000000000(0000) GS:ffff888126274000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff7fa235e00 CR3: 0000000027fde000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 udelay include/asm-generic/delay.h:62 [inline]
 wait_for_lsr+0x166/0x2f0 drivers/tty/serial/8250/8250_port.c:1976
 serial8250_fifo_wait_for_lsr_thre drivers/tty/serial/8250/8250_port.c:3207 [inline]
 serial8250_console_fifo_write drivers/tty/serial/8250/8250_port.c:3272 [inline]
 serial8250_console_write+0x120d/0x1b90 drivers/tty/serial/8250/8250_port.c:3357
 console_emit_next_record kernel/printk/printk.c:3163 [inline]
 console_flush_one_record+0x68b/0xb90 kernel/printk/printk.c:3269
 legacy_kthread_func+0x1b6/0x250 kernel/printk/printk.c:3712
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (124):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/16 02:45 upstream d458a240344c 81fb92f3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/05/12 09:17 upstream 50897c955902 07aeade5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/04/09 08:14 upstream 7f87a5ea75f0 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/03/08 15:51 upstream c23719abc330 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/03/07 00:03 upstream 651690480a96 41d8037d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/02/22 10:23 upstream fa5c82f4d2bb 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/02/17 01:31 upstream c22e26bd0906 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/02/08 07:19 upstream e7aa57247700 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/20 14:35 upstream 24d479d26b25 06648d9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/18 10:15 upstream d12453c7e281 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/18 06:21 upstream d12453c7e281 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/17 23:44 upstream d3eeb99bbc99 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/17 16:18 upstream d3eeb99bbc99 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/16 09:45 upstream 603c05a1639f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/16 07:14 upstream 603c05a1639f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/15 19:48 upstream 944aacb68baf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/15 06:15 upstream 944aacb68baf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/13 16:54 upstream b71e635feefc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/10 06:01 upstream 372800cb95a3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/09 16:46 upstream 623fb9912f6a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/08 01:08 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/07 16:35 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/07 06:50 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/07 03:40 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/07 00:04 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/06 17:13 upstream 7f98ab9da046 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/06 11:47 upstream 7f98ab9da046 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/06 08:10 upstream 7f98ab9da046 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2026/01/01 10:13 upstream 349bd28a86f2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/31 16:39 upstream c8ebd433459b d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/31 00:58 upstream dbf8fe85a16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/28 18:19 upstream d26143bb38e2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/28 09:28 upstream d26143bb38e2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/27 22:47 upstream c53f467229a7 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/27 04:28 upstream 3f0e9c8cefa9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/26 19:36 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/26 06:20 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/25 22:06 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/25 13:33 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/24 16:00 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/22 21:42 upstream 9448598b22c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/22 16:15 upstream 9448598b22c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/22 15:05 upstream 9448598b22c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/20 14:30 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/20 10:58 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/05/19 04:38 upstream a5806cd506af f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/05/11 12:57 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in sb_start_write
2025/12/02 04:57 linux-next 7d31f578f323 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in sb_start_write
2025/03/11 02:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0a6021b3fc20 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in sb_start_write
* Struck through repros no longer work on HEAD.