From: syzbot <syzbot+c6a1953c27ace6cc34e5@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in wdm_rxwork/usb_submit_urb (2)
Date: Wed, 24 Apr 2024 21:40:22 -0700 [thread overview]
Message-ID: <00000000000092e8f90616e4627f@google.com> (raw)
In-Reply-To: <000000000000d23cfc061133c3ae@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: a160e1202ca3 usb: dwc3: qcom: Add multiport suspend/resume..
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=12b37a9b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fe204286ac73e15
dashboard link: https://syzkaller.appspot.com/bug?extid=c6a1953c27ace6cc34e5
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1492bcef180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166f3d27180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/17ff4370c4e0/disk-a160e120.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ef5dd31b4c4/vmlinux-a160e120.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f0fdddbf376c/bzImage-a160e120.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c6a1953c27ace6cc34e5@syzkaller.appspotmail.com
------------[ cut here ]------------
URB ffff8881022a5e00 submitted while active
WARNING: CPU: 1 PID: 35 at drivers/usb/core/urb.c:379 usb_submit_urb+0x14da/0x1730 drivers/usb/core/urb.c:379
Modules linked in:
CPU: 1 PID: 35 Comm: kworker/1:1 Not tainted 6.9.0-rc5-syzkaller-00104-ga160e1202ca3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events wdm_rxwork
RIP: 0010:usb_submit_urb+0x14da/0x1730 drivers/usb/core/urb.c:379
Code: fe eb cb bb fe ff ff ff e9 c1 f3 ff ff e8 1e ea 2c fd c6 05 81 4e 68 05 01 90 48 c7 c7 60 a3 30 87 48 89 de e8 a7 1a f3 fc 90 <0f> 0b 90 90 e9 b6 fe ff ff bb f8 ff ff ff e9 91 f3 ff ff 48 89 ef
RSP: 0018:ffffc90000257c20 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8881022a5e00 RCX: ffffffff811902c9
RDX: ffff888102efba00 RSI: ffffffff811902d6 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000293
R13: ffff88810abe8090 R14: ffff88810abe8050 R15: ffffffff899ade98
FS: 0000000000000000(0000) GS:ffff8881f6500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564d6da62000 CR3: 0000000115de4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
wdm_rxwork+0xf3/0x200 drivers/usb/class/cdc-wdm.c:989
process_one_work+0x9a9/0x1ac0 kernel/workqueue.c:3254
process_scheduled_works kernel/workqueue.c:3335 [inline]
worker_thread+0x6c8/0xf70 kernel/workqueue.c:3416
kthread+0x2c1/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
---
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.
prev parent reply other threads:[~2024-04-25 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 18:51 [syzbot] [usb?] WARNING in wdm_rxwork/usb_submit_urb (2) syzbot
2024-04-25 4:40 ` syzbot [this message]
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=00000000000092e8f90616e4627f@google.com \
--to=syzbot+c6a1953c27ace6cc34e5@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).