From: syzbot <syzbot+0c3370f235b74b3cfd97@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hdanton@sina.com, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: INFO: trying to register non-static key in io_cqring_ev_posted (2)
Date: Tue, 31 Mar 2020 04:14:03 -0700 [thread overview]
Message-ID: <000000000000533b4505a224aa8b@google.com> (raw)
In-Reply-To: <0000000000002efe6505a221d5be@google.com>
syzbot has bisected this bug to:
commit b41e98524e424d104aa7851d54fd65820759875a
Author: Jens Axboe <axboe@kernel.dk>
Date: Mon Feb 17 16:52:41 2020 +0000
io_uring: add per-task callback handler
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=115adadbe00000
start commit: 673b41e0 staging/octeon: fix up merge error
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=135adadbe00000
console output: https://syzkaller.appspot.com/x/log.txt?x=155adadbe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=acf766c0e3d3f8c6
dashboard link: https://syzkaller.appspot.com/bug?extid=0c3370f235b74b3cfd97
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ac1b9de00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10449493e00000
Reported-by: syzbot+0c3370f235b74b3cfd97@syzkaller.appspotmail.com
Fixes: b41e98524e42 ("io_uring: add per-task callback handler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-31 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 7:51 INFO: trying to register non-static key in io_cqring_ev_posted (2) syzbot
2020-03-31 11:14 ` syzbot [this message]
[not found] <20200331114459.17184-1-hdanton@sina.com>
2020-03-31 14:53 ` Jens Axboe
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=000000000000533b4505a224aa8b@google.com \
--to=syzbot+0c3370f235b74b3cfd97@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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