INFO: task hung in dev_ioctl

7 views
Skip to first unread message

syzbot

unread,
Apr 19, 2022, 9:11:20 AM4/19/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 74766a973637 Linux 4.14.275
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17c25768f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=78767ee43940f0a8
dashboard link: https://syzkaller.appspot.com/bug?extid=ed546be1c19859a4ae88
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ed546b...@syzkaller.appspotmail.com

Bluetooth: hci2 command 0x0406 tx timeout
Bluetooth: hci4 command 0x0406 tx timeout
Bluetooth: hci5 command 0x0406 tx timeout
Bluetooth: hci3 command 0x0406 tx timeout
Bluetooth: hci1 command 0x0406 tx timeout
INFO: task systemd-udevd:10565 blocked for more than 140 seconds.
Not tainted 4.14.275-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
systemd-udevd D28512 10565 4626 0x00000300
Call Trace:
context_switch kernel/sched/core.c:2811 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3387
schedule+0x8d/0x1b0 kernel/sched/core.c:3431
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3489
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x669/0x1310 kernel/locking/mutex.c:893
dev_ioctl+0x6e5/0xbe0 net/core/dev_ioctl.c:490
sock_do_ioctl net/socket.c:981 [inline]
sock_ioctl+0x164/0x4c0 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Aug 17, 2022, 9:11:16 AM8/17/22
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages