From: syzbot <syzbot+7170d66493145b71afd4@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, brauner@kernel.org,
dan.carpenter@oracle.com, dvyukov@google.com,
liam.howlett@oracle.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
wanjiabing@vivo.com, willy@infradead.org
Subject: Re: [syzbot] KASAN: use-after-free Read in mas_next_nentry
Date: Wed, 25 Jan 2023 14:04:17 -0800 [thread overview]
Message-ID: <0000000000004dc42605f31dd05c@google.com> (raw)
In-Reply-To: <0000000000009ecbf205dda227bd@google.com>
syzbot suspects this issue was fixed by commit:
commit 59f2f4b8a757412fce372f6d0767bdb55da127a8
Author: Liam Howlett <liam.howlett@oracle.com>
Date: Mon Nov 7 20:11:42 2022 +0000
fs/userfaultfd: Fix maple tree iterator in userfaultfd_unregister()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=129e8afe480000
start commit: b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=7170d66493145b71afd4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11bfb2a9880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b1d319880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/userfaultfd: Fix maple tree iterator in userfaultfd_unregister()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-25 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 12:43 [syzbot] KASAN: use-after-free Read in mas_next_nentry syzbot
2022-04-27 12:55 ` Christian Brauner
2022-04-27 14:58 ` Matthew Wilcox
2022-04-27 15:17 ` Liam Howlett
2022-04-27 15:22 ` Dmitry Vyukov
2022-04-28 6:23 ` Dan Carpenter
2023-01-25 22:04 ` syzbot [this message]
2023-01-26 13:14 ` Liam R. Howlett
2023-01-27 7:09 ` Dmitry Vyukov
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=0000000000004dc42605f31dd05c@google.com \
--to=syzbot+7170d66493145b71afd4@syzkaller.appspotmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=brauner@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wanjiabing@vivo.com \
--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