From: syzbot <syzbot+76629376e06e2c2ad626@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, hdanton@sina.com, johan@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
paskripkin@gmail.com, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in hub_port_init (2)
Date: Thu, 20 Jan 2022 00:11:10 -0800 [thread overview]
Message-ID: <000000000000836a4805d5ff0b2b@google.com> (raw)
In-Reply-To: <20220120080020.2619-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+76629376e06e2c2ad626@syzkaller.appspotmail.com
Tested on:
commit: 6f59bc24 Add linux-next specific files for 20220118
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
kernel config: https://syzkaller.appspot.com/x/.config?x=94e8da4df9ab6319
dashboard link: https://syzkaller.appspot.com/bug?extid=76629376e06e2c2ad626
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=101ba7efb00000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-01-20 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220120080020.2619-1-hdanton@sina.com>
2022-01-20 8:11 ` syzbot [this message]
2022-01-20 17:28 ` [syzbot] INFO: task hung in hub_port_init (2) Alan Stern
2022-01-20 17:55 ` syzbot
2022-01-24 20:23 ` [PATCH] USB: core: Fix hang in usb_kill_urb by adding memory barriers Alan Stern
2021-11-16 2:47 [syzbot] INFO: task hung in hub_port_init (2) syzbot
2022-01-19 20:16 ` syzbot
2022-09-19 1:54 ` 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=000000000000836a4805d5ff0b2b@google.com \
--to=syzbot+76629376e06e2c2ad626@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=stern@rowland.harvard.edu \
--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 NNTP newsgroup(s).