From: Jens Axboe <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] KASAN: use-after-free Read in add_wait_queue
Date: Tue, 22 Mar 2022 18:08:16 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/22/22 5:37 PM, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 91eac1c69c202d9dad8bf717ae5b92db70bfe5cf
> Author: Jens Axboe <[email protected]>
> 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=1280c825700000
> 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=1180c825700000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1680c825700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=63af44f0631a5c3a
> dashboard link: https://syzkaller.appspot.com/bug?extid=950cee6d91e62329be2c
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14506ddb700000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=139b2093700000
>
> Reported-by: [email protected]
> Fixes: 91eac1c69c20 ("io_uring: cache poll/double-poll state with a request flag")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz test: git://git.kernel.dk/linux-block for-5.18/io_uring
All three reports are the same thing...
--
Jens Axboe
next prev parent reply other threads:[~2022-03-23 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:52 [syzbot] KASAN: use-after-free Read in add_wait_queue syzbot
2022-03-22 20:55 ` syzbot
2022-03-22 20:58 ` Jens Axboe
2022-03-22 21:15 ` syzbot
2022-03-22 23:37 ` syzbot
2022-03-23 0:08 ` Jens Axboe [this message]
2022-03-23 0:48 ` syzbot
2022-04-28 15:34 ` syzbot
2022-04-28 15:39 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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