syzbot


INFO: task hung in dev_ioctl

Status: upstream: reported on 2024/05/22 11:00
Reported-by: syzbot+7fb31d286a22077b740f@syzkaller.appspotmail.com
First crash: 63d, last: 57d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in dev_ioctl (4) net 1 1164d 1164d 0/27 auto-closed as invalid on 2021/08/15 15:56
linux-4.14 INFO: task hung in dev_ioctl 1 827d 827d 0/1 auto-closed as invalid on 2022/08/17 13:11
android-49 INFO: task hung in dev_ioctl 1 2209d 2209d 0/3 auto-closed as invalid on 2019/02/22 12:59
upstream INFO: task hung in dev_ioctl (2) net 1 1922d 1922d 0/27 closed as invalid on 2019/05/08 13:05
android-414 INFO: task hung in dev_ioctl 2 2126d 2146d 0/1 auto-closed as invalid on 2019/03/27 22:33
android-414 INFO: task hung in dev_ioctl (2) 1 1699d 1698d 0/1 auto-closed as invalid on 2020/03/28 22:15
linux-6.1 INFO: task hung in dev_ioctl 3 37d 54d 0/3 upstream: reported on 2024/05/31 11:34
upstream INFO: task hung in rtnetlink_rcv_msg net C inconclusive inconclusive 1970 15d 1979d 27/27 fixed on 2024/07/09 19:14
upstream INFO: task hung in dev_ioctl net 2 2123d 2151d 0/27 auto-closed as invalid on 2019/03/30 00:48
upstream INFO: task hung in dev_ioctl (3) net 7 1300d 1429d 0/27 auto-closed as invalid on 2021/04/01 04:28
upstream INFO: task hung in dev_ioctl (5) net 20 1007d 1052d 0/27 auto-closed as invalid on 2022/01/19 01:57

Sample crash report:
INFO: task syz-executor.4:5832 blocked for more than 143 seconds.
      Not tainted 5.15.160-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:25312 pid: 5832 ppid:  5138 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 dev_ioctl+0x598/0xf60 net/core/dev_ioctl.c:611
 sock_ioctl+0x68f/0x770 net/socket.c:1184
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7feb14787ee9
RSP: 002b:00007feb12cfb0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007feb148bef80 RCX: 00007feb14787ee9
RDX: 0000000020000340 RSI: 00000000000089f1 RDI: 0000000000000006
RBP: 00007feb147d447f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007feb148bef80 R15: 00007ffc64077838
 </TASK>
INFO: task syz-executor.4:5833 blocked for more than 143 seconds.
      Not tainted 5.15.160-syzkaller #0
"echo 0 > /proc/sys/

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/28 06:33 linux-5.15.y c61bd26ae81a f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in dev_ioctl
2024/05/22 11:00 linux-5.15.y 83655231580b 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in dev_ioctl
* Struck through repros no longer work on HEAD.