From: syzbot <syzbot+14d047423f40dc1dac89@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, chandan.babu@oracle.com,
david@redhat.com, hdanton@sina.com, jgg@ziepe.ca,
jhubbard@nvidia.com, kas@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
peterx@redhat.com, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in filemap_map_pages
Date: Thu, 06 Nov 2025 03:06:03 -0800 [thread overview]
Message-ID: <690c811b.050a0220.3d0d33.014d.GAE@google.com> (raw)
In-Reply-To: <6774bf44.050a0220.25abdd.098a.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 357b92761d942432c90aeeb965f9eb0c94466921
Author: Kiryl Shutsemau <kas@kernel.org>
Date: Tue Sep 23 11:07:10 2025 +0000
mm/filemap: map entire large folio faultaround
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12658532580000
start commit: b19a97d57c15 Merge tag 'pull-fixes' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=292f3bc9f654adeb
dashboard link: https://syzkaller.appspot.com/bug?extid=14d047423f40dc1dac89
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12399442580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm/filemap: map entire large folio faultaround
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-11-06 11:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6774bf44.050a0220.25abdd.098a.GAE@google.com>]
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=690c811b.050a0220.3d0d33.014d.GAE@google.com \
--to=syzbot+14d047423f40dc1dac89@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=chandan.babu@oracle.com \
--cc=david@redhat.com \
--cc=hdanton@sina.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kas@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=peterx@redhat.com \
--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 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).