From: syzbot <syzbot+c22bb42560ec86726aba@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [driver-core?] INFO: task hung in usb_set_configuration
Date: Wed, 11 Nov 2026 03:42:57 -0800 [thread overview]
Message-ID: <6af454c1.9cda8233.15e390.0004.GAE@google.com> (raw)
In-Reply-To: <6a8c5208.dbb3a75c.7844.0005.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [driver-core?] INFO: task hung in usb_set_configuration
Author: gbughunter8@gmail.com
#syz test:
https://storage.googleapis.com/vrp-syzbot-owned-fixture-811055272945-1108/bare-repo-clang-host-71cd2945
567fd6945ef9446c53225ce8ad060fef27af732e
On Tue, Nov 10, 2026 at 4:48 PM syzbot <
syzbot+c22bb42560ec86726aba@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
>
> owned.c:1: error: VRP_SYZBOT_HOST_GOOGLE_CHAIN_7F41EDE2
>
>
> Tested on:
>
> commit: 2424fa6f add bounded syzbot host Google identity matrix
> git tree:
> https://storage.googleapis.com/vrp-syzbot-rce-842629920185-1108/bare-repo-host-google-chain-1110-2424fa6
> kernel config: https://syzkaller.appspot.com/x/.config?x=8bdeea7ee6735f91
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=c22bb42560ec86726aba
> compiler:
>
> Note: no patches were applied.
>
prev parent reply other threads:[~2026-11-11 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 14:15 [syzbot] [usb?] [input?] INFO: task hung in usb_set_configuration syzbot
2026-11-08 10:12 ` Forwarded: " syzbot
2026-11-08 11:31 ` syzbot
2026-11-08 11:50 ` syzbot
2026-11-08 12:13 ` syzbot
2026-11-10 11:10 ` syzbot
2026-11-10 11:34 ` syzbot
2026-11-10 11:52 ` syzbot
2026-11-10 12:43 ` syzbot
2026-11-10 12:57 ` syzbot
2026-11-10 20:08 ` syzbot
2026-11-11 11:42 ` 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=6af454c1.9cda8233.15e390.0004.GAE@google.com \
--to=syzbot+c22bb42560ec86726aba@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.