From: syzbot <syzbot+b4a81dc8727e513f364d@syzkaller.appspotmail.com>
To: alaaemadhossney.ae@gmail.com, asml.silence@gmail.com,
axboe@kernel.dk, christian@brauner.io,
gregkh@linuxfoundation.org, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, shankarkoli@quadrogen.com,
shuah@kernel.org, skhan@linuxfoundation.org,
syzkaller-bugs@googlegroups.com, valentina.manea.m@gmail.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] general protection fault in try_to_wake_up (2)
Date: Mon, 10 May 2021 23:58:05 -0700 [thread overview]
Message-ID: <000000000000749f0605c2086a95@google.com> (raw)
In-Reply-To: <000000000000b304d505bc3e5b3a@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=114c0579d00000
start commit: d4961772 Merge tag 'clk-fixes-for-linus' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9320464bf47598bd
dashboard link: https://syzkaller.appspot.com/bug?extid=b4a81dc8727e513f364d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126d1de9d00000
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
prev parent reply other threads:[~2021-05-11 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 14:48 general protection fault in try_to_wake_up (2) syzbot
2021-05-11 6:58 ` 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=000000000000749f0605c2086a95@google.com \
--to=syzbot+b4a81dc8727e513f364d@syzkaller.appspotmail.com \
--cc=alaaemadhossney.ae@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shankarkoli@quadrogen.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=valentina.manea.m@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).