mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+592e2ab8775dbe0bf09a@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] INFO: task hung in uevent_show (2)
Date: Thu, 10 Jul 2025 04:59:02 -0700	[thread overview]
Message-ID: <686fab06.a00a0220.26a83e.0011.GAE@google.com> (raw)
In-Reply-To: <20250710110510.3162-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: task hung in usbdev_ioctl

INFO: task syz.1.17:6837 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc4-syzkaller-00314-gb4b4dbfa96de-dirty #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.17        state:D stack:24088 pid:6837  tgid:6836  ppid:6635   task_flags:0x400040 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5396 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6785
 __schedule_loop kernel/sched/core.c:6863 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6878
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6935
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x65d/0xc70 kernel/locking/mutex.c:747
 device_lock include/linux/device.h:884 [inline]
 usbdev_do_ioctl drivers/usb/core/devio.c:2611 [inline]
 usbdev_ioctl+0x140/0x20c0 drivers/usb/core/devio.c:2827
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:907 [inline]
 __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fddcf58d169
RSP: 002b:00007fddd03af038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fddcf7a5fa0 RCX: 00007fddcf58d169
RDX: 0000000000000000 RSI: 0000000041045508 RDI: 0000000000000003
RBP: 00007fddcf60e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fddcf7a5fa0 R15: 00007fff1a55f668
 </TASK>
INFO: task syz.1.17:6837 is blocked on a mutex likely owned by task kworker/1:4:5945.
task:kworker/1:4     state:S stack:22472 pid:5945  tgid:5945  ppid:2      task_flags:0x4208060 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5396 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6785
 __schedule_loop kernel/sched/core.c:6863 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6878
 schedule_timeout+0x9a/0x270 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:95 [inline]
 __wait_for_common+0x3d7/0x710 kernel/sched/completion.c:116
 wait_for_common kernel/sched/completion.c:127 [inline]
 wait_for_completion_interruptible+0x1f/0x40 kernel/sched/completion.c:216
 send_packet+0x63b/0xae0 drivers/media/rc/imon.c:649
 imon_init_rdev drivers/media/rc/imon.c:1990 [inline]
 imon_init_intf0 drivers/media/rc/imon.c:2279 [inline]
 imon_probe+0x1f7e/0x3410 drivers/media/rc/imon.c:2436
 usb_probe_interface+0x644/0xbc0 drivers/usb/core/driver.c:396
 call_driver_probe drivers/base/dd.c:-1 [inline]
 really_probe+0x26d/0x9a0 drivers/base/dd.c:657
 __driver_probe_device+0x18c/0x2f0 drivers/base/dd.c:799
 driver_probe_device+0x4f/0x430 drivers/base/dd.c:829
 __device_attach_driver+0x2ce/0x530 drivers/base/dd.c:957
 bus_for_each_drv+0x24e/0x2e0 drivers/base/bus.c:462
 __device_attach+0x2b8/0x400 drivers/base/dd.c:1029
 bus_probe_device+0x185/0x260 drivers/base/bus.c:537
 device_add+0x7b6/0xb50 drivers/base/core.c:3692
 usb_set_configuration+0x1a87/0x20e0 drivers/usb/core/message.c:2210
 usb_generic_driver_probe+0x8d/0x150 drivers/usb/core/generic.c:250
 usb_probe_device+0x1c4/0x390 drivers/usb/core/driver.c:291
 call_driver_probe drivers/base/dd.c:-1 [inline]
 really_probe+0x26d/0x9a0 drivers/base/dd.c:657
 __driver_probe_device+0x18c/0x2f0 drivers/base/dd.c:799
 driver_probe_device+0x4f/0x430 drivers/base/dd.c:829
 __device_attach_driver+0x2ce/0x530 drivers/base/dd.c:957
 bus_for_each_drv+0x24e/0x2e0 drivers/base/bus.c:462
 __device_attach+0x2b8/0x400 drivers/base/dd.c:1029
 bus_probe_device+0x185/0x260 drivers/base/bus.c:537


Tested on:

commit:         b4b4dbfa media: stk1160: use usb_alloc_noncoherent/usb..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=170c9bd4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b49da22b2184ad70
dashboard link: https://syzkaller.appspot.com/bug?extid=592e2ab8775dbe0bf09a
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch:          https://syzkaller.appspot.com/x/patch.diff?x=152f5a8c580000


  reply	other threads:[~2025-07-10 11:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09 14:37 [syzbot] [usb?] " syzbot
2024-11-10  0:59 ` syzbot
2025-07-10 11:05   ` Hillf Danton
2025-07-10 11:59     ` syzbot [this message]
2025-07-10 12:59   ` Hillf Danton
2025-07-10 13:25     ` [syzbot] [kernel?] " syzbot
2025-07-09  4:39 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-09 14:03   ` [syzbot] [kernel?] " syzbot
2025-07-09 14:13     ` Tetsuo Handa
2025-07-09 14:27       ` Alan Stern
2025-07-09 14:44         ` Tetsuo Handa
2025-07-09 15:19           ` Alan Stern
2025-07-09 15:33             ` Tetsuo Handa
2025-07-09 15:41               ` Alan Stern
2025-07-10 10:17                 ` Tetsuo Handa
2025-07-10 14:13                   ` Alan Stern
2025-07-09 14:15   ` [syzbot] [usb?] " Tetsuo Handa
2025-07-09 14:44     ` [syzbot] [kernel?] " syzbot
2025-07-09 15:01       ` Tetsuo Handa
2025-07-11 11:09     ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 11:44       ` [syzbot] [kernel?] " syzbot
2025-07-11 11:52       ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 12:13         ` [syzbot] [kernel?] " syzbot
2025-07-11 13:34         ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 14:09           ` [syzbot] [kernel?] " syzbot
2025-07-11 15:01           ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 15:46             ` [syzbot] [kernel?] " syzbot
2025-07-12 14:40             ` [syzbot] [usb?] " Tetsuo Handa
2025-07-12 15:18               ` [syzbot] [kernel?] " syzbot
2025-07-12 15:41               ` [syzbot] [usb?] " Tetsuo Handa
2025-07-12 17:43                 ` [syzbot] [kernel?] " syzbot
2025-07-13  7:50                 ` [PATCH] media: imon: make send_packet() more robust Tetsuo Handa
2025-07-13  8:11                   ` Hillf Danton
2025-07-13 15:21                     ` Alan Stern
2025-07-15 20:19                       ` Sean Young
2025-07-16  1:30                         ` Alan Stern
2025-07-16  9:38                           ` Sean Young
2025-07-16 10:09                             ` Tetsuo Handa
2025-07-16 11:55                               ` Hillf Danton
2025-07-16 12:47                               ` Sean Young
2025-07-16 14:07                                 ` [PATCH v2] " Tetsuo Handa
2025-07-16 14:45                                   ` Alan Stern
2025-07-17 14:21                                     ` [PATCH v3] " Tetsuo Handa
2025-07-16 14:38                             ` [PATCH] " Alan Stern
2025-07-13  8:29                   ` [syzbot] [kernel?] INFO: task hung in uevent_show (2) syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=686fab06.a00a0220.26a83e.0011.GAE@google.com \
    --to=syzbot+592e2ab8775dbe0bf09a@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome