From: syzbot <syzbot+31ae6d17d115e980fd14@syzkaller.appspotmail.com>
To: brouer@redhat.com, coreteam@netfilter.org, davem@davemloft.net,
edumazet@google.com, eman.mohamed@rofaidarealestate.com,
gregkh@linuxfoundation.org, gustavoars@kernel.org,
hdanton@sina.com, ingrassia@epigenesys.com, johan@kernel.org,
kaber@trash.net, kadlec@blackhole.kfki.hu,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mathias.nyman@linux.intel.com, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
skhan@linuxfoundation.org, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in usb_get_descriptor
Date: Sat, 12 Feb 2022 14:43:15 -0800 [thread overview]
Message-ID: <000000000000b15b3505d7d9e8ca@google.com> (raw)
In-Reply-To: <0000000000004c57c005b0fc4114@google.com>
syzbot suspects this issue was fixed by commit:
commit 363eaa3a450abb4e63bd6e3ad79d1f7a0f717814
Author: Shuah Khan <skhan@linuxfoundation.org>
Date: Tue Mar 30 01:36:51 2021 +0000
usbip: synchronize event handler with sysfs code paths
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1616e872700000
start commit: 4fa56ad0d12e Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=144ecdb0be3abc07
dashboard link: https://syzkaller.appspot.com/bug?extid=31ae6d17d115e980fd14
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12548d11d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ec77e9d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: usbip: synchronize event handler with sysfs code paths
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-12 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 8:19 INFO: task hung in usb_get_descriptor syzbot
2022-02-12 22:43 ` syzbot [this message]
2022-05-12 13:19 ` [syzbot] " Dmitry Vyukov
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=000000000000b15b3505d7d9e8ca@google.com \
--to=syzbot+31ae6d17d115e980fd14@syzkaller.appspotmail.com \
--cc=brouer@redhat.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eman.mohamed@rofaidarealestate.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=hdanton@sina.com \
--cc=ingrassia@epigenesys.com \
--cc=johan@kernel.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=skhan@linuxfoundation.org \
--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).