From: syzbot <syzbot+0d818c0d39399188f393@syzkaller.appspotmail.com>
To: axboe@kernel.dk, io-uring@vger.kernel.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, liuyun01@kylinos.cn,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: INFO: trying to register non-static key in io_cqring_ev_posted
Date: Wed, 20 Nov 2019 21:56:00 -0800 [thread overview]
Message-ID: <000000000000ab834f0597d4f337@google.com> (raw)
In-Reply-To: <00000000000072cb6c0597635d04@google.com>
syzbot has bisected this bug to:
commit 206aefde4f886fdeb3b6339aacab3a85fb74cb7e
Author: Jens Axboe <axboe@kernel.dk>
Date: Fri Nov 8 01:27:42 2019 +0000
io_uring: reduce/pack size of io_ring_ctx
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f98af2e00000
start commit: 5d1131b4 Add linux-next specific files for 20191119
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=17f98af2e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f98af2e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b60c562d89e5a8df
dashboard link: https://syzkaller.appspot.com/bug?extid=0d818c0d39399188f393
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=169b29d2e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b3956ae00000
Reported-by: syzbot+0d818c0d39399188f393@syzkaller.appspotmail.com
Fixes: 206aefde4f88 ("io_uring: reduce/pack size of io_ring_ctx")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2019-11-21 5:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <00000000000072cb6c0597635d04@google.com>]
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=000000000000ab834f0597d4f337@google.com \
--to=syzbot+0d818c0d39399188f393@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
--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;
as well as URLs for NNTP newsgroup(s).