[v6.6] INFO: task hung in tty_open
0 views
Skip to first unread message
syzbot
Jul 31, 2026, 11:41:32 AM (10 days ago) Jul 31
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: a1153c0deb44 Linux 6.6.147
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12acd499580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0bc3d90c30838b5
dashboard link: https://syzkaller.appspot.com/bug?extid=0d02b4d8ca27fa6fab68
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f646bfa1b52/disk-a1153c0d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a2aec2e8f0fd/vmlinux-a1153c0d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a7abe1f87405/bzImage-a1153c0d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0d02b4...@syzkaller.appspotmail.com
INFO: task syz.6.451:7543 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.451 state:D stack:27912 pid:7543 ppid:7339 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5382 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6701
schedule+0xbd/0x170 kernel/sched/core.c:6775
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6834
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x673/0xc80 kernel/locking/mutex.c:747
tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
chrdev_open+0x58c/0x600 fs/char_dev.c:414
do_dentry_open+0x880/0x14b0 fs/open.c:929
do_open fs/namei.c:3640 [inline]
path_openat+0x284f/0x3270 fs/namei.c:3801
do_filp_open+0x1f2/0x430 fs/namei.c:3828
do_sys_openat2+0x134/0x1d0 fs/open.c:1422
do_sys_open fs/open.c:1437 [inline]
__do_sys_openat fs/open.c:1453 [inline]
__se_sys_openat fs/open.c:1448 [inline]
__x64_sys_openat+0x139/0x160 fs/open.c:1448
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcef039e019
RSP: 002b:00007fceee5f6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fcef0625fa0 RCX: 00007fcef039e019
RDX: 0000000000000001 RSI: 0000200000000080 RDI: ffffffffffffff9c
RBP: 00007fcef043500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcef0626038 R14: 00007fcef0625fa0 R15: 00007fffdf1ebb08
</TASK>
Showing all locks held in the system:
2 locks held by kworker/u4:0/11:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90000107d00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90000107d00 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
3 locks held by kworker/u4:1/12:
1 lock held by khungtaskd/29:
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by kworker/u4:7/1093:
2 locks held by kworker/u4:10/4861:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc9000fbe7d00 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc9000fbe7d00 ((reaper_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
2 locks held by getty/5527:
#0: ffff8880315e20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
4 locks held by syz.2.392/7270:
1 lock held by syz.6.451/7543:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.8.467/7800:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.9.539/8032:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.7.558/8123:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.0.637/8570:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.3.699/8839:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.1.712/8889:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.4.721/9009:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.5.742/9321:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.9.834/9934:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.7.835/9947:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by rm/10202:
1 lock held by syz.2.883/10203:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: a1153c0deb44 Linux 6.6.147
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12acd499580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0bc3d90c30838b5
dashboard link: https://syzkaller.appspot.com/bug?extid=0d02b4d8ca27fa6fab68
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f646bfa1b52/disk-a1153c0d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a2aec2e8f0fd/vmlinux-a1153c0d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a7abe1f87405/bzImage-a1153c0d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0d02b4...@syzkaller.appspotmail.com
INFO: task syz.6.451:7543 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.451 state:D stack:27912 pid:7543 ppid:7339 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5382 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6701
schedule+0xbd/0x170 kernel/sched/core.c:6775
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6834
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x673/0xc80 kernel/locking/mutex.c:747
tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
chrdev_open+0x58c/0x600 fs/char_dev.c:414
do_dentry_open+0x880/0x14b0 fs/open.c:929
do_open fs/namei.c:3640 [inline]
path_openat+0x284f/0x3270 fs/namei.c:3801
do_filp_open+0x1f2/0x430 fs/namei.c:3828
do_sys_openat2+0x134/0x1d0 fs/open.c:1422
do_sys_open fs/open.c:1437 [inline]
__do_sys_openat fs/open.c:1453 [inline]
__se_sys_openat fs/open.c:1448 [inline]
__x64_sys_openat+0x139/0x160 fs/open.c:1448
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcef039e019
RSP: 002b:00007fceee5f6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fcef0625fa0 RCX: 00007fcef039e019
RDX: 0000000000000001 RSI: 0000200000000080 RDI: ffffffffffffff9c
RBP: 00007fcef043500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcef0626038 R14: 00007fcef0625fa0 R15: 00007fffdf1ebb08
</TASK>
Showing all locks held in the system:
2 locks held by kworker/u4:0/11:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90000107d00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90000107d00 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
3 locks held by kworker/u4:1/12:
1 lock held by khungtaskd/29:
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by kworker/u4:7/1093:
2 locks held by kworker/u4:10/4861:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc9000fbe7d00 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc9000fbe7d00 ((reaper_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
2 locks held by getty/5527:
#0: ffff8880315e20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
4 locks held by syz.2.392/7270:
1 lock held by syz.6.451/7543:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.8.467/7800:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.9.539/8032:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.7.558/8123:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.0.637/8570:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.3.699/8839:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.1.712/8889:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.4.721/9009:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.5.742/9321:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.9.834/9934:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.7.835/9947:
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
#0: ffffffff8d8b76c8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by rm/10202:
1 lock held by syz.2.883/10203:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Aug 3, 2026, 9:33:37 AM (8 days ago) Aug 3
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: fb28aa725e05 Linux 6.1.180
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13ebec9e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=7079ad18402f43113752
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz.3.736:6368 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.736 state:D stack:27760 pid:6368 ppid:4273 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7dd/0x10b0 fs/open.c:882
do_open fs/namei.c:3634 [inline]
path_openat+0x2674/0x2f10 fs/namei.c:3791
do_filp_open+0x1ee/0x420 fs/namei.c:3818
do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_openat fs/open.c:1352 [inline]
__se_sys_openat fs/open.c:1347 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1347
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa09b99e019
RSP: 002b:00007fa09c817028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fa09bc25fa0 RCX: 00007fa09b99e019
RDX: 0000000000088002 RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007fa09ba3500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa09bc26038 R14: 00007fa09bc25fa0 R15: 00007fff61fcafd8
</TASK>
INFO: task syz.5.733:6478 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.733 state:D stack:27920 pid:6478 ppid:6384 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7dd/0x10b0 fs/open.c:882
do_open fs/namei.c:3634 [inline]
path_openat+0x2674/0x2f10 fs/namei.c:3791
do_filp_open+0x1ee/0x420 fs/namei.c:3818
do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_openat fs/open.c:1352 [inline]
__se_sys_openat fs/open.c:1347 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1347
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7efd4bf9e019
RSP: 002b:00007efd4ce88028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007efd4c225fa0 RCX: 00007efd4bf9e019
RDX: 0000000000000002 RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007efd4c03500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007efd4c226038 R14: 00007efd4c225fa0 R15: 00007ffdaea4ba88
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
Showing all locks held in the system:
#0: ffffffff8cb2e4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2ed10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6527
2 locks held by getty/4028:
#0: ffff88803018a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41e/0x1360 drivers/tty/n_tty.c:2198
3 locks held by kworker/0:3/4261:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90003d57d00 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:104
3 locks held by syz.0.704/6302:
1 lock held by syz.3.736/6368:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.5.733/6478:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
6 locks held by kworker/0:17/6513:
#0: ffff88823bdcef38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900036d7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffff888144fb5190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#2: ffff888144fb5190 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5200 drivers/usb/core/hub.c:5845
#3: ffff888056019190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#3: ffff888056019190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
#4: ffff8880555da118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#4: ffff8880555da118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:1009
#5: ffff8880790a6758 (radio_keene:326:(hdl)->_lock){+.+.}-{3:3}, at: v4l2_ctrl_handler_setup+0x4f/0x90 drivers/media/v4l2-core/v4l2-ctrls-core.c:2233
3 locks held by kworker/u4:15/7311:
3 locks held by kworker/u4:23/7327:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90003937d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
4 locks held by kworker/u4:24/7329:
1 lock held by syz.2.954/7371:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.2.954/7372:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.1.1053/7700:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
4 locks held by udevd/8114:
#0: ffff8880758010a0 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
#1: ffff888055b59888 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x59/0x410 fs/kernfs/file.c:172
#2: ffff8880366a6008 (kn->active#5){++++}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff8880366a6008 (kn->active#5){++++}-{0:0}, at: kernfs_seq_start+0xae/0x410 fs/kernfs/file.c:173
#3: ffff888056019190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#3: ffff888056019190 (&dev->mutex){....}-{3:3}, at: uevent_show+0x16e/0x320 drivers/base/core.c:2669
1 lock held by syz.9.1175/8152:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz-executor/8884:
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
1 lock held by syz.4.1394/8985:
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
2 locks held by sed/8993:
=============================================
NMI backtrace for cpu 0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf0e/0xf50 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
syzbot
Aug 4, 2026, 1:29:45 PM (6 days ago) Aug 4
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 6e2fd6534337 Linux 5.15.213
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10ac4bb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=522be398b7bc5889e97f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d7b46606b13d/disk-6e2fd653.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/da120fdeb081/vmlinux-6e2fd653.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c2643457e3f/bzImage-6e2fd653.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz.6.325:5497 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.325 state:D stack:25296 pid: 5497 ppid: 5221 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11c3/0x4350 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
__mutex_lock_common+0xdf5/0x2400 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7f7/0xf90 fs/open.c:826
do_open fs/namei.c:3616 [inline]
path_openat+0x2718/0x2fb0 fs/namei.c:3750
do_filp_open+0x1df/0x400 fs/namei.c:3777
do_sys_openat2+0x14b/0x500 fs/open.c:1255
do_sys_open fs/open.c:1271 [inline]
__do_sys_openat fs/open.c:1287 [inline]
__se_sys_openat fs/open.c:1282 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1282
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f7ac9a8b019
RSP: 002b:00007f7ac7ce3028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f7ac9d12fa0 RCX: 00007f7ac9a8b019
RDX: 0000000000123e00 RSI: 00002000000003c0 RDI: ffffffffffffff9c
RBP: 00007f7ac9b2200c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7ac9d13038 R14: 00007f7ac9d12fa0 R15: 00007ffe860a4f48
</TASK>
INFO: task syz.1.342:5561 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.342 state:D stack:27888 pid: 5561 ppid: 4186 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11c3/0x4350 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
__mutex_lock_common+0xdf5/0x2400 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7f7/0xf90 fs/open.c:826
do_open fs/namei.c:3616 [inline]
path_openat+0x2718/0x2fb0 fs/namei.c:3750
do_filp_open+0x1df/0x400 fs/namei.c:3777
do_sys_openat2+0x14b/0x500 fs/open.c:1255
do_sys_open fs/open.c:1271 [inline]
__do_sys_openat fs/open.c:1287 [inline]
__se_sys_openat fs/open.c:1282 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1282
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fc147071019
RSP: 002b:00007fc1452c9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fc1472f8fa0 RCX: 00007fc147071019
RDX: 0000000000000100 RSI: 0000200000000140 RDI: ffffffffffffff9c
RBP: 00007fc14710800c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc1472f9038 R14: 00007fc1472f8fa0 R15: 00007ffe79481088
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
Showing all locks held in the system:
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/154:
2 locks held by kworker/u4:4/2302:
2 locks held by getty/3945:
#0: ffff88802c437098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:8/4366:
5 locks held by kworker/0:11/4369:
3 locks held by syz.4.202/4934:
1 lock held by syz.6.325/5497:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.1.342/5561:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.7.485/6199:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.503/6302:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.9.536/6466:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.3.568/6693:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.6.608/6958:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.6.608/6964:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.6.608/6965:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.6.608/6969:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.1.632/7181:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.0.634/7190:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.4.668/7592:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.9.660/7693:
#0: ffffffff8c9f62e8 (
tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.3.721/7957:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
2 locks held by syz-executor/8128:
1 lock held by syz.5.765/8233:
#0: ffff888018f8d528 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888018f8d528 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x16c/0x2d0 mm/util.c:549
1 lock held by syz.5.765/8234:
2 locks held by syz.8.768/8246:
#0: ffffc900049bb250 (&kvm->lock){+.+.}-{3:3}, at: kvm_arch_vm_ioctl+0x7f4/0x1530 arch/x86/kvm/x86.c:6115
#1: ffffc900049b90a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_pic_init+0x18f/0x2f0 arch/x86/kvm/i8259.c:606
1 lock held by syz.8.768/8250:
#0: ffffc900049bb250 (&kvm->lock){+.+.}-{3:3}, at: kvm_vm_ioctl_create_vcpu+0x58/0x820 virt/kvm/kvm_main.c:3696
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe1b/0xe60 kernel/hung_task.c:369
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
Reply all
Reply to author
Forward
0 new messages