From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+85439002c78b774488d8@syzkaller.appspotmail.com>
Cc: erosca@de.adit-jv.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Oliver Neukum <oneukum@suse.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
zakia@firesystem.co.nz
Subject: Re: [syzbot] INFO: task hung in usb_remote_wakeup (2)
Date: Mon, 19 Apr 2021 09:11:22 +0200 [thread overview]
Message-ID: <CACT4Y+YYphSF5ygTNDdBWpGZaNgEtRCquj-XSTRqWn3va_LOYg@mail.gmail.com> (raw)
In-Reply-To: <000000000000d91f7905c028bbf4@google.com>
On Sat, Apr 17, 2021 at 12:41 PM syzbot
<syzbot+85439002c78b774488d8@syzkaller.appspotmail.com> wrote:
>
> 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
Looks reasonable:
#syz fix: usbip: synchronize event handler with sysfs code paths
prev parent reply other threads:[~2021-04-19 7:11 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] " syzbot
2021-04-19 7:11 ` Dmitry Vyukov [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=CACT4Y+YYphSF5ygTNDdBWpGZaNgEtRCquj-XSTRqWn3va_LOYg@mail.gmail.com \
--to=dvyukov@google.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=syzbot+85439002c78b774488d8@syzkaller.appspotmail.com \
--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.