syzbot


INFO: task hung in sys_io_uring_register

Status: upstream: reported on 2024/03/31 12:11
Reported-by: syzbot+af196205a2ef7bbad377@syzkaller.appspotmail.com
First crash: 36d, last: 36d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in sys_io_uring_register fs 1 865d 861d 0/26 auto-closed as invalid on 2022/03/23 08:02
upstream INFO: task hung in sys_io_uring_register (2) io-uring syz error error 2 435d 431d 0/26 auto-obsoleted due to no activity on 2023/06/25 22:43

Sample crash report:
INFO: task syz-executor.3:7517 blocked for more than 143 seconds.
      Not tainted 5.15.153-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3  state:D stack:    0 pid: 7517 ppid:  4536 flags:0x00000005
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0xf10/0x1e48 kernel/sched/core.c:6376
 schedule+0x11c/0x1c8 kernel/sched/core.c:6459
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6518
 __mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 __do_sys_io_uring_register io_uring/io_uring.c:11042 [inline]
 __se_sys_io_uring_register io_uring/io_uring.c:11020 [inline]
 __arm64_sys_io_uring_register+0x1bc/0x2e7c io_uring/io_uring.c:11020
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffff800014ae14a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
2 locks held by kworker/u4:5/599:
 #0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
 #1: ffff80001dae7c00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
2 locks held by getty/3717:
 #0: ffff0000d2c99098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
 #1: ffff800018dd32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
1 lock held by syz-executor.2/7409:
2 locks held by syz-executor.3/7516:
1 lock held by syz-executor.3/7517:
 #0: ffff0000ce3b60a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __do_sys_io_uring_register io_uring/io_uring.c:11042 [inline]
 #0: ffff0000ce3b60a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __se_sys_io_uring_register io_uring/io_uring.c:11020 [inline]
 #0: ffff0000ce3b60a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __arm64_sys_io_uring_register+0x1bc/0x2e7c io_uring/io_uring.c:11020
2 locks held by syz-executor.4/8253:

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/31 12:11 linux-5.15.y 9465fef4ae35 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in sys_io_uring_register
* Struck through repros no longer work on HEAD.