From: syzbot <syzbot+cd301bb6523ea8cc8ca2@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
gregkh@linuxfoundation.org, io-uring@vger.kernel.org,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in io_poll_remove_entries
Date: Tue, 22 Mar 2022 20:25:12 -0700 [thread overview]
Message-ID: <00000000000008409805dada47ce@google.com> (raw)
In-Reply-To: <0000000000000f361d05dacabb09@google.com>
syzbot has bisected this issue to:
commit 91eac1c69c202d9dad8bf717ae5b92db70bfe5cf
Author: Jens Axboe <axboe@kernel.dk>
Date: Wed Mar 16 22:59:10 2022 +0000
io_uring: cache poll/double-poll state with a request flag
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11819d0b700000
start commit: b47d5a4f6b8d Merge tag 'audit-pr-20220321' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13819d0b700000
console output: https://syzkaller.appspot.com/x/log.txt?x=15819d0b700000
kernel config: https://syzkaller.appspot.com/x/.config?x=c44f0c051803a0ae
dashboard link: https://syzkaller.appspot.com/bug?extid=cd301bb6523ea8cc8ca2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150525ed700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d08625700000
Reported-by: syzbot+cd301bb6523ea8cc8ca2@syzkaller.appspotmail.com
Fixes: 91eac1c69c20 ("io_uring: cache poll/double-poll state with a request flag")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-03-23 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:52 [syzbot] KASAN: use-after-free Read in io_poll_remove_entries syzbot
2022-03-23 1:20 ` syzbot
2022-03-23 1:22 ` Jens Axboe
2022-03-23 5:00 ` syzbot
2022-03-23 3:25 ` 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=00000000000008409805dada47ce@google.com \
--to=syzbot+cd301bb6523ea8cc8ca2@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.