From: syzbot <syzbot+85439002c78b774488d8@syzkaller.appspotmail.com>
To: erosca@de.adit-jv.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
oneukum@suse.com, skhan@linuxfoundation.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
zakia@firesystem.co.nz
Subject: Re: [syzbot] INFO: task hung in usb_remote_wakeup (2)
Date: Sat, 17 Apr 2021 03:41:06 -0700 [thread overview]
Message-ID: <000000000000d91f7905c028bbf4@google.com> (raw)
In-Reply-To: <00000000000082554705ba5fe454@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=16c89e91d00000
start commit: bec4c296 Merge tag 'ecryptfs-5.11-rc6-setxattr-fix' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9408d1770a50819c
dashboard link: https://syzkaller.appspot.com/bug?extid=85439002c78b774488d8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138d0264d00000
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:[~2021-04-17 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:58 INFO: task hung in usb_remote_wakeup (2) syzbot
2021-04-17 10:41 ` syzbot [this message]
2021-04-19 7:11 ` [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=000000000000d91f7905c028bbf4@google.com \
--to=syzbot+85439002c78b774488d8@syzkaller.appspotmail.com \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=skhan@linuxfoundation.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zakia@firesystem.co.nz \
/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.