From: syzbot <syzbot+12056a09a0311d758e60@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
egiptomarmol@loucastone.com, hdanton@sina.com,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mail@anirudhrb.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
willy@infradead.org
Subject: Re: [syzbot] KASAN: use-after-free Read in idr_for_each (2)
Date: Thu, 15 Apr 2021 11:28:15 -0700 [thread overview]
Message-ID: <000000000000d45f8005c00706a1@google.com> (raw)
In-Reply-To: <000000000000ca835605b0e8a723@google.com>
syzbot suspects this issue was fixed by commit:
commit 61cf93700fe6359552848ed5e3becba6cd760efa
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Mon Mar 8 14:16:16 2021 +0000
io_uring: Convert personality_idr to XArray
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16f91b9ad00000
start commit: dd86e7fa Merge tag 'pci-v5.11-fixes-2' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e83e68d0a6aba5f6
dashboard link: https://syzkaller.appspot.com/bug?extid=12056a09a0311d758e60
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174b80ef500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165522d4d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: Convert personality_idr to XArray
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-04-15 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 8:56 KASAN: use-after-free Read in idr_for_each (2) syzbot
2020-11-28 17:19 ` syzbot
2020-12-18 15:43 ` Pavel Begunkov
2020-12-18 16:44 ` syzbot
2021-03-19 10:38 ` Pavel Begunkov
2021-03-19 11:02 ` [syzbot] " syzbot
2021-04-15 18:28 ` syzbot [this message]
2021-04-19 12:09 ` Pavel Begunkov
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=000000000000d45f8005c00706a1@google.com \
--to=syzbot+12056a09a0311d758e60@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=egiptomarmol@loucastone.com \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).