[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67687395.050a0220.2f3838.000a.GAE@google.com>
Date: Sun, 22 Dec 2024 12:16:21 -0800
From: syzbot <syzbot+64d45c23acffac0fb82d@...kaller.appspotmail.com>
To: anna-maria@...utronix.de, frederic@...nel.org,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: [syzbot] [usb?] INFO: task hung in do_syscall_64 (3)
Hello,
syzbot found the following issue on:
HEAD commit: 499551201b5f Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16287e0f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=64d45c23acffac0fb82d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14506f30580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7e67f36abfb2/disk-49955120.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cbd5df554814/vmlinux-49955120.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26aa1e962905/bzImage-49955120.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+64d45c23acffac0fb82d@...kaller.appspotmail.com
INFO: task udevd:6008 blocked for more than 185 seconds.
Not tainted 6.13.0-rc3-syzkaller-00209-g499551201b5f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd state:R running task stack:25048 pid:6008 tgid:6008 ppid:5205 flags:0x00000002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5369 [inline]
__schedule+0x1850/0x4c30 kernel/sched/core.c:6756
__schedule_loop kernel/sched/core.c:6833 [inline]
schedule+0x14b/0x320 kernel/sched/core.c:6848
schedule_hrtimeout_range_clock+0x223/0x320 kernel/time/sleep_timeout.c:207
ep_poll fs/eventpoll.c:2099 [inline]
do_epoll_wait+0x1db4/0x21c0 fs/eventpoll.c:2484
__do_sys_epoll_wait fs/eventpoll.c:2492 [inline]
__se_sys_epoll_wait fs/eventpoll.c:2487 [inline]
__x64_sys_epoll_wait+0x257/0x2a0 fs/eventpoll.c:2487
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8692523457
RSP: 002b:00007ffe04d8b468 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8692523457
RDX: 0000000000000004 RSI: 00007ffe04d8b4a8 RDI: 0000000000000004
RBP: 0000558d225ede80 R08: 0000000000000007 R09: 6bcd4ee305e41824
R10: 00000000ffffffff R11: 0000000000000246 R12: 0000558d225f34c0
R13: 00007ffe04d8b4a8 R14: 00000000ffffffff R15: 0000558d225cd910
</TASK>
INFO: task kworker/0:7:6050 blocked for more than 146 seconds.
Not tainted 6.13.0-rc3-syzkaller-00209-g499551201b5f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:7 state:D stack:20696 pid:6050 tgid:6050 ppid:2 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5369 [inline]
__schedule+0x1850/0x4c30 kernel/sched/core.c:6756
__schedule_loop kernel/sched/core.c:6833 [inline]
schedule+0x14b/0x320 kernel/sched/core.c:6848
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6905
__mutex_lock_common kernel/locking/mutex.c:665 [inline]
__mutex_lock+0x7e7/0xee0 kernel/locking/mutex.c:735
__input_unregister_device+0x2f3/0x620 drivers/input/input.c:2277
input_unregister_device+0xa3/0x100 drivers/input/input.c:2516
imon_init_intf0 drivers/media/rc/imon.c:2289 [inline]
imon_probe+0x264e/0x31b0 drivers/media/rc/imon.c:2434
usb_probe_interface+0x641/0xbb0 drivers/usb/core/driver.c:396
really_probe+0x2b8/0xad0 drivers/base/dd.c:658
__driver_probe_device+0x1a2/0x390 drivers/base/dd.c:800
driver_probe_device+0x50/0x430 drivers/base/dd.c:830
__device_attach_driver+0x2d6/0x530 drivers/base/dd.c:958
bus_for_each_drv+0x24e/0x2e0 drivers/base/bus.c:459
__device_attach+0x333/0x520 drivers/base/dd.c:1030
bus_probe_device+0x189/0x260 drivers/base/bus.c:534
device_add+0x856/0xbf0 drivers/base/core.c:3665
usb_set_configuration+0x1976/0x1fb0 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x88/0x140 drivers/usb/core/generic.c:254
usb_probe_device+0x1b8/0x380 drivers/usb/core/driver.c:291
really_probe+0x2b8/0xad0 drivers/base/dd.c:658
__driver_probe_device+0x1a2/0x390 drivers/base/dd.c:800
driver_probe_device+0x50/0x430 drivers/base/dd.c:830
__device_attach_driver+0x2d6/0x530 drivers/base/dd.c:958
bus_for_each_drv+0x24e/0x2e0 drivers/base/bus.c:459
__device_attach+0x333/0x520 drivers/base/dd.c:1030
bus_probe_device+0x189/0x260 drivers/base/bus.c:534
device_add+0x856/0xbf0 drivers/base/core.c:3665
usb_new_device+0x104a/0x19a0 drivers/usb/core/hub.c:2651
hub_port_connect drivers/usb/core/hub.c:5521 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5661 [inline]
port_event drivers/usb/core/hub.c:5821 [inline]
hub_event+0x2d6d/0x5150 drivers/usb/core/hub.c:5903
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310
---
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 syzkaller@...glegroups.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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
Powered by blists - more mailing lists