From: Liam Howlett <liam.howlett@oracle.com>
To: syzbot <syzbot+99551d8b4d180f6cb1c0@syzkaller.appspotmail.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"ccross@google.com" <ccross@google.com>,
"david@redhat.com" <david@redhat.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"willy@infradead.org" <willy@infradead.org>
Subject: Re: [syzbot] KASAN: use-after-free Read in exit_mmap
Date: Thu, 28 Jul 2022 17:53:17 +0000 [thread overview]
Message-ID: <20220728175310.6kynllh2cvdw4ooo@revolver> (raw)
In-Reply-To: <0000000000006de26305e4cd37ae@google.com>
* syzbot <syzbot+99551d8b4d180f6cb1c0@syzkaller.appspotmail.com> [220727 14:02]:
> syzbot has bisected this issue to:
>
> commit e23cb70bcbef5c189790042d1d6d89e33308c386
> Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
> Date: Tue Jun 21 20:47:14 2022 +0000
>
> mm: remove the vma linked list
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1078f202080000
> start commit: cb71b93c2dc3 Add linux-next specific files for 20220628
> git tree: linux-next
> final oops: https://syzkaller.appspot.com/x/report.txt?x=1278f202080000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1478f202080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=badbc1adb2d582eb
> dashboard link: https://syzkaller.appspot.com/bug?extid=99551d8b4d180f6cb1c0
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=117dc816080000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12695b26080000
>
> Reported-by: syzbot+99551d8b4d180f6cb1c0@syzkaller.appspotmail.com
> Fixes: e23cb70bcbef ("mm: remove the vma linked list")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Thanks. I tested this against the most recent patches with the above
kernel config and the issue has already been resolved.
prev parent reply other threads:[~2022-07-28 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:11 syzbot
[not found] ` <0000000000006de26305e4cd37ae@google.com>
2022-07-28 17:53 ` Liam Howlett [this message]
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=20220728175310.6kynllh2cvdw4ooo@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=ccross@google.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+99551d8b4d180f6cb1c0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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