From: syzbot <syzbot+68771c0e74f7bb7804e5@syzkaller.appspotmail.com>
To: Liam.Howlett@Oracle.com, akpm@linux-foundation.org,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] KASAN: use-after-free Read in __vma_adjust
Date: Sun, 12 Jun 2022 15:08:08 -0700 [thread overview]
Message-ID: <0000000000000d20dc05e14768b5@google.com> (raw)
In-Reply-To: <000000000000c0517405e13dc59e@google.com>
syzbot has bisected this issue to:
commit d3ccd17e7c9647b956d415acdf3e3fde7ae9e20c
Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
Date: Thu Jun 9 20:57:09 2022 +0000
mm: start tracking VMAs with maple tree
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11463853f00000
start commit: 6d0c80680317 Add linux-next specific files for 20220610
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13463853f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15463853f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a30d6e3e814e5931
dashboard link: https://syzkaller.appspot.com/bug?extid=68771c0e74f7bb7804e5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e632bbf00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103df80ff00000
Reported-by: syzbot+68771c0e74f7bb7804e5@syzkaller.appspotmail.com
Fixes: d3ccd17e7c96 ("mm: start tracking VMAs with maple tree")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-12 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 10:38 [syzbot] KASAN: use-after-free Read in __vma_adjust syzbot
2022-06-12 22:08 ` syzbot [this message]
2022-06-15 16:45 ` Liam Howlett
[not found] <20220613104713.1829-1-hdanton@sina.com>
2022-06-13 12:47 ` syzbot
[not found] <20220614105010.1897-1-hdanton@sina.com>
2022-06-14 11:09 ` syzbot
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=0000000000000d20dc05e14768b5@google.com \
--to=syzbot+68771c0e74f7bb7804e5@syzkaller.appspotmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.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 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.