From: syzbot <syzbot+950cee6d91e62329be2c@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 add_wait_queue
Date: Thu, 28 Apr 2022 08:34:13 -0700 [thread overview]
Message-ID: <000000000000765a6105ddb8a8b9@google.com> (raw)
In-Reply-To: <00000000000012e22c05dacabb11@google.com>
syzbot suspects this issue was fixed by commit:
commit d89a4fac0fbc6fe5fc24d1c9a889440dcf410368
Author: Jens Axboe <axboe@kernel.dk>
Date: Tue Mar 22 19:11:28 2022 +0000
io_uring: fix assuming triggered poll waitqueue is the single poll
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b70e42f00000
start commit: b47d5a4f6b8d Merge tag 'audit-pr-20220321' of git://git.ke..
git tree: upstream
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
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: fix assuming triggered poll waitqueue is the single poll
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-04-28 15:34 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
2022-03-23 0:48 ` syzbot
2022-04-28 15:34 ` syzbot [this message]
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 \
--in-reply-to=000000000000765a6105ddb8a8b9@google.com \
--to=syzbot+950cee6d91e62329be2c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox