syzbot


INFO: task hung in exit_aio (5)

Status: upstream: reported on 2026/05/17 16:41
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+4c9b421ef4f6c18a174e@syzkaller.appspotmail.com
First crash: 321d, last: 4d15h
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
ec3aa5ac-7111-40fe-befc-fb6cb7cf5216 assessment-security 💥 INFO: task hung in exit_aio (5) 2026/05/14 11:20 2026/05/14 11:20 2026/05/14 11:21 6ccb967e465e832a7bfd7a116ad00d52a0923a5d failed to run ["git" "pull" "origin" "HEAD" "--depth=1" "--allow-unrelated-histories"]: exit status 128 From /app/workdir/repo/linux * branch HEAD -> FETCH_HEAD Updating files: 20% (19410/93697) Updating files: 21% (19677/93697) Updating files: 22% (20614/93697) Updating files: 23% (21551/93697) Updating files: 24% (22488/93697) Updating files: 25% (23425/93697) Updating files: 26% (24362/93697) Updating files: 27% (25299/93697) Updating files: 28% (26236/93697) Updating files: 29% (27173/93697) Updating files: 30% (28110/93697) Updating files: 30% (28829/93697) Updating files: 31% (29047/93697) Updating files: 32% (29984/93697) Updating files: 33% (30921/93697) Updating files: 34% (31857/93697) error: unable to write file drivers/clk/qcom/clk-regmap-mux-div.h error: unable to write file drivers/clk/qcom/clk-regmap-mux.c error: unable to write file drivers/clk/qcom/clk-regmap-mux.h error: unable to write file drivers/clk/qcom/clk-regmap-phy-mux.c error: unable to write file drivers/clk/qcom/clk-regmap-phy-mux.h error: unable to write file drivers/clk/qcom/clk-regmap.c error: unable to write file drivers/clk/qcom/clk-regmap.h error: unable to write file drivers/clk/qcom/clk-rpm.c error: unable to write file drivers/clk/qcom/clk-rpmh.c error: unable to write file drivers/clk/qcom/clk-smd-rpm.c error: unable to write file drivers/clk/qcom/clk-spmi-pmic-div.c error: unable to write file drivers/clk/qcom/common.c error: unable to write file drivers/clk/qcom/common.h error: unable to write file drivers/clk/qcom/dispcc-eliza.c error: unable to write file drivers/clk/qcom/dispcc-glymur.c error: unable to write file drivers/clk/qcom/dispcc-kaanapali.c error: unable to write file drivers/clk/qcom/dispcc-milos.c error: unable to write file drivers/clk/qcom/dispcc-qcm2290.c error: unable to write file drivers/clk/qcom/dispcc-qcs615.c error: unable to write file drivers/clk/qcom/dispcc-sc7180.c error: unable to write file drivers/clk/qcom/dispcc-sc7280.c error: unable to write file drivers/clk/qcom/dispcc-sc8280xp.c error: unable to write file drivers/clk/qcom/dispcc-sdm845.c error: unable to write file drivers/clk/qcom/dispcc-sm4450.c error: unable to write file drivers/clk/qcom/dispcc-sm6115.c error: unable to write file drivers/clk/qcom/dispcc-sm6125.c error: unable to write file drivers/clk/qcom/dispcc-sm6350.c error: unable to write file drivers/clk/qcom/dispcc-sm6375.c error: unable to write file drivers/clk/qcom/dispcc-sm7150.c error: unable to write file drivers/clk/qcom/dispcc-sm8250.c error: unable to write file drivers/clk/qcom/dispcc-sm8450.c error: unable to write file drivers/clk/qcom/dispcc-sm8550.c error: unable to write file drivers/clk/qcom/dispcc-sm8750.c error: unable to write file drivers/clk/qcom/dispcc-x1e80100.c error: unable to write file drivers/clk/qcom/dispcc0-sa8775p.c error: unable to write file drivers/clk/qcom/dispcc1-sa8775p.c error: unable to write file drivers/clk/qcom/ecpricc-qdu1000.c error: unable to write file drivers/clk/qcom/gcc-apq8084.c error: unable to write file drivers/clk/qcom/gcc-eliza.c error: unable to write file drivers/clk/qcom/gcc-glymur.c error: unable to write file drivers/clk/qcom/gcc-ipq4019.c error: unable to write file drivers/clk/qcom/gcc-ipq5018.c error: unable to write file drivers/clk/qcom/gcc-ipq5210.c error: unable to write file drivers/clk/qcom/gcc-ipq5332.c error: unable to write file drivers/clk/qcom/gcc-ipq5424.c error: unable to write file drivers/clk/qcom/gcc-ipq6018.c error: unable to write file drivers/clk/qcom/gcc-ipq806x.c error: unable to write file drivers/clk/qcom/gcc-ipq8074.c error: unable to write file drivers/clk/qcom/gcc-ipq9574.c error: unable to write file drivers/clk/qcom/gcc-kaanapali.c error: unable to write file drivers/clk/qcom/gcc-mdm9607.c error: unable to write file drivers/clk/qcom/gcc-mdm9615.c error: unable to write file drivers/clk/qcom/gcc-milos.c error: unable to write file drivers/clk/qcom/gcc-msm8660.c error: unable to write file drivers/clk/qcom/gcc-msm8909.c error: unable to write file drivers/c
fe59251d-8627-4ac4-8279-04c7677ec2d5 repro INFO: task hung in exit_aio (5) 2026/03/06 13:52 2026/03/06 13:52 2026/03/06 14:02 31e9c887f7dc24e04b3ca70d0d54fc34141844b0
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] INFO: task hung in exit_aio (5) 0 (1) 2026/05/17 16:41
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-6-12 INFO: task hung in exit_aio (2) 1 20 6h27m 109d 0/1 premoderation: reported on 2026/02/04 00:47
upstream INFO: task hung in exit_aio (4) fs 1 6 527d 593d 0/29 auto-obsoleted due to no activity on 2025/03/13 05:51
android-414 INFO: task hung in exit_aio 1 3 2577d 2578d 0/1 auto-closed as invalid on 2019/10/25 08:40
upstream INFO: task hung in exit_aio (2) fs 1 3 1654d 1732d 0/29 closed as invalid on 2022/02/07 19:09
upstream INFO: task hung in exit_aio (3) fs 1 1 687d 687d 0/29 auto-obsoleted due to no activity on 2024/10/04 00:29
android-6-12 INFO: task hung in exit_aio 1 38 193d 335d 0/1 auto-obsoleted due to no activity on 2026/01/04 12:01
upstream INFO: task hung in exit_aio fs 1 C 17519 2472d 3087d 0/29 closed as dup on 2018/04/08 22:50

Sample crash report:
INFO: task syz.6.2770:15099 blocked for more than 144 seconds.
      Tainted: G             L      syzkaller #0
      Blocked by coredump.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.2770      state:D stack:28632 pid:15099 tgid:15095 ppid:13231  task_flags:0x40044c flags:0x00080001
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
 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:100 [inline]
 __wait_for_common kernel/sched/completion.c:121 [inline]
 wait_for_common kernel/sched/completion.c:132 [inline]
 wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153
 exit_aio+0x319/0x3f0 fs/aio.c:981
 __mmput+0x68/0x3d0 kernel/fork.c:1175
 exit_mm+0x1f6/0x2d0 kernel/exit.c:582
 do_exit+0x6a2/0x22c0 kernel/exit.c:964
 do_group_exit+0x21b/0x2d0 kernel/exit.c:1119
 get_signal+0x1284/0x1330 kernel/signal.c:3037
 arch_do_signal_or_restart+0xbc/0x840 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
 exit_to_user_mode_loop+0x8c/0x4d0 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline]
 do_syscall_64+0x33e/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8211cace59[ 1376.148301][   T38] RIP: 0033:0x7f8211cace59
RSP: 002b:00007f820fee5028 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: 0000000000010106 RBX: 00007f8211f26090 RCX: 00007f8211cace59
RDX: 0000000000010106 RSI: 00002000000000c0 RDI: 0000000000000005
RBP: 00007f8211d42d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8211f26128 R14: 00007f8211f26090 R15: 00007ffd9332f688
 </TASK>

Showing all locks held in the system:
4 locks held by rcuc/1/28:
1 lock held by khungtaskd/38:
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/u8:2/42:
 #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: ffffc90000b37c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90000b37c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8dfce230 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
5 locks held by kworker/u8:9/1772:
3 locks held by kworker/u8:10/2977:
 #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: ffffc9000e33fc40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000e33fc40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8dfce230 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
2 locks held by getty/5353:
 #0: ffff88803641b0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003cbe2e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13a0 drivers/tty/n_tty.c:2211
3 locks held by kworker/u8:15/6177:
 #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: ffffc90004c77c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90004c77c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8dfce230 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
4 locks held by kworker/1:6/10987:
3 locks held by kworker/u8:18/12079:
 #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: ffffc90005c5fc40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005c5fc40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f3584f8 (rtnl_mutex){+.+.}-{4:4}, at: linkwatch_event+0xe/0x60 net/core/link_watch.c:313
2 locks held by syz-executor/13294:
1 lock held by syz-executor/13328:
1 lock held by syz-executor/13348:
 #0: ffff88805faa6480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
3 locks held by kworker/u8:19/13750:
 #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: ffffc90005467c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005467c40 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8dfce230 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
10 locks held by kworker/u8:24/14740:
7 locks held by syz-executor/15186:
 #0: ffff8880365f4480 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2724 [inline]
 #0: ffff8880365f4480 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x22d/0xba0 fs/read_write.c:684
 #1: ffff88803b895c78 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
 #2: ffff888028f30e18 (kn->active#52){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff888028f30e18 (kn->active#52){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x540 fs/kernfs/file.c:344
 #3: ffffffff8ebd04b8 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd7/0x370 drivers/net/netdevsim/bus.c:234
 #4: ffff88805e8c0160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline]
 #4: ffff88805e8c0160 (&dev->mutex){....}-{4:4}, at: __device_driver_lock drivers/base/dd.c:1174 [inline]
 #4: ffff88805e8c0160 (&dev->mutex){....}-{4:4}, at: device_release_driver_internal+0xb6/0x870 drivers/base/dd.c:1372
 #5: ffff88801e2d4310 (&devlink->lock_key#3){+.+.}-{4:4}, at: nsim_drv_remove+0x50/0x160 drivers/net/netdevsim/dev.c:1799
 #6: ffffffff8dfce230 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:3828
4 locks held by syz-executor/15554:
 #0: ffff8880365f4480 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2724 [inline]
 #0: ffff8880365f4480 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x22d/0xba0 fs/read_write.c:684
 #1: ffff888093712c78 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
 #2: ffff888028f30e18 (kn->active#52){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff888028f30e18 (kn->active#52){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x540 fs/kernfs/file.c:344
 #3: ffffffff8ebd04b8 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd7/0x370 drivers/net/netdevsim/bus.c:234
4 locks held by syz.8.2957/15786:
1 lock held by syz-executor/15789:
 #0: ffffffff8f3584f8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff8f3584f8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline]
 #0: ffffffff8f3584f8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x883/0x1bb0 net/core/rtnetlink.c:4109
2 locks held by syz-executor/15819:
 #0: ffffffff8f3497a0 (pernet_ops_rwsem){++++}-{4:4}, at: copy_net_ns+0x4f7/0x730 net/core/net_namespace.c:575
 #1: ffffffff8f3584f8 (rtnl_mutex){+.+.}-{4:4}, at: ip_tunnel_init_net+0x2d7/0x840 net/ipv4/ip_tunnel.c:1146
2 locks held by syz.1.2976/15864:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 38 Comm: khungtaskd Tainted: G             L      syzkaller #0 PREEMPT_{RT,(full)} 
Tainted: [L]=SOFTLOCKUP
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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 17 Comm: pr/legacy Tainted: G             L      syzkaller #0 PREEMPT_{RT,(full)} 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:io_serial_in+0x77/0xc0 drivers/tty/serial/8250/8250_port.c:401
Code: e8 4e 01 90 fc 44 89 f9 d3 e3 49 83 ee 80 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 0f 10 f7 fc 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f c3 cc cc cc cc cc 44 89 f9 80 e1 07
RSP: 0000:ffffc900001679d0 EFLAGS: 00000202
RAX: 1ffffffff3363e00 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffffff99b1f970 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffffff853477f0 R12: dffffc0000000000
R13: 0000000000000000 R14: ffffffff99b1f6e0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888126171000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c230000 CR3: 000000003a0cc000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000423
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 serial_in drivers/tty/serial/8250/8250.h:128 [inline]
 serial_lsr_in drivers/tty/serial/8250/8250.h:150 [inline]
 wait_for_lsr+0x1aa/0x2f0 drivers/tty/serial/8250/8250_port.c:1970
 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 (32):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/20 03:13 upstream 27fa82620cba 0909d65f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/05/20 03:06 upstream 27fa82620cba 0909d65f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/05/13 16:33 upstream 1d5dcaa3bd65 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/04/26 05:59 upstream 897d54018cc9 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/04/12 21:59 upstream f5459048c38a 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in exit_aio
2026/03/19 11:22 upstream 8a30aeb0d1b4 bd6dcb30 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/02/07 09:21 upstream 2687c848e578 f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2026/01/15 03:37 upstream 944aacb68baf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in exit_aio
2026/01/01 08:36 upstream 9528d5c091c5 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/12/27 04:22 upstream 3f0e9c8cefa9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/11/25 19:21 upstream 8a2bcda5e139 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/11/19 00:30 upstream 5bebe8de1926 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/11/16 06:06 upstream f824272b6e3f f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/11/11 14:23 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/10/17 21:40 upstream cf1ea8854e4f 7adf5298 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/10/06 13:23 upstream fd94619c4336 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/10/01 23:00 upstream d3479214c05d a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/10/01 06:06 upstream 50c19e20ed2e 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/29 11:41 upstream e5f0a698b34e 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/28 19:05 upstream 8f9736633f8c 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/25 11:01 upstream bf40f4b87761 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/08 20:03 upstream f777d1112ee5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/06 00:00 upstream d1d10cea0895 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/05 10:47 upstream d69eb204c255 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/04 10:11 upstream b9a10f876409 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/02 23:25 upstream e6b9dce0aeeb 091ba174 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/09/02 14:05 upstream b320789d6883 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/08/31 03:57 upstream c8bc81a52d5a 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/08/29 00:33 upstream 07d9df80082b 3e1beec6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/08/28 11:00 upstream 07d9df80082b 443c11c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in exit_aio
2025/07/06 22:24 linux-next 26ffb3d6f02c 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in exit_aio
2025/08/07 15:37 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next 21ef6a269833 04cffc22 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 INFO: task hung in exit_aio
* Struck through repros no longer work on HEAD.