From: syzbot <syzbot+ec4b7d82bb051330f15a@syzkaller.appspotmail.com>
To: Liam.Howlett@Oracle.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, david@redhat.com, hdanton@sina.com,
hughd@google.com, jannh@google.com, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz, vivek.kasireddy@intel.com, willy@infradead.org
Subject: Re: [syzbot] [mm?] BUG: Bad page map (8)
Date: Fri, 27 Dec 2024 09:02:04 -0800 [thread overview]
Message-ID: <676edd8c.050a0220.2f3838.0487.GAE@google.com> (raw)
In-Reply-To: <000000000000341f5f061d8d6bcb@google.com>
syzbot suspects this issue was fixed by commit:
commit 79f3d123caedbac30a6fd75f9597b2a60a89d513
Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
Date: Wed Oct 16 01:34:55 2024 +0000
mm/mmap: fix race in mmap_region() with ftruncate()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17d2d018580000
start commit: 3efc57369a0c Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a4fcb065287cdb84
dashboard link: https://syzkaller.appspot.com/bug?extid=ec4b7d82bb051330f15a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113acd9f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cc0127980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm/mmap: fix race in mmap_region() with ftruncate()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-27 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 22:51 syzbot
2024-07-19 11:21 ` David Hildenbrand
2024-07-20 5:02 ` Hillf Danton
2024-07-20 6:30 ` Kasireddy, Vivek
2024-07-22 13:23 ` David Hildenbrand
2024-07-20 6:32 ` Kasireddy, Vivek
2024-07-20 7:01 ` syzbot
2024-09-30 0:02 ` syzbot
2024-09-30 13:52 ` Matthew Wilcox
2024-12-27 17:02 ` syzbot [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=676edd8c.050a0220.2f3838.0487.GAE@google.com \
--to=syzbot+ec4b7d82bb051330f15a@syzkaller.appspotmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hdanton@sina.com \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=vivek.kasireddy@intel.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