From: syzbot <syzbot+20ed41006cf9d842c2b5@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
brad.spengler@opensrcsec.com, jannh@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
pfalcato@suse.de, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in vma_merge_existing_range
Date: Sun, 23 Mar 2025 17:31:06 -0700 [thread overview]
Message-ID: <67e0a7ca.050a0220.21942d.000a.GAE@google.com> (raw)
In-Reply-To: <67dc67f0.050a0220.25ae54.001e.GAE@google.com>
syzbot has bisected this issue to:
commit 47b16d0462a460000b8f05dfb1292377ac48f3ca
Author: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Date: Sat Feb 22 16:19:52 2025 +0000
mm: abort vma_modify() on merge out of memory failure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1415fe98580000
start commit: 586de92313fc Merge tag 'i2c-for-6.14-rc8' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1615fe98580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1215fe98580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2e330e9768b5b8ff
dashboard link: https://syzkaller.appspot.com/bug?extid=20ed41006cf9d842c2b5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1196f3b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d3dc4c580000
Reported-by: syzbot+20ed41006cf9d842c2b5@syzkaller.appspotmail.com
Fixes: 47b16d0462a4 ("mm: abort vma_modify() on merge out of memory failure")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-24 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 19:09 syzbot
2025-03-20 20:02 ` Pedro Falcato
2025-03-20 20:02 ` syzbot
2025-03-20 20:11 ` Jann Horn
2025-03-20 20:53 ` Lorenzo Stoakes
2025-03-20 23:04 ` Jann Horn
2025-03-21 9:10 ` Lorenzo Stoakes
2025-03-23 16:49 ` syzbot
2025-03-24 0:31 ` 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=67e0a7ca.050a0220.21942d.000a.GAE@google.com \
--to=syzbot+20ed41006cf9d842c2b5@syzkaller.appspotmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brad.spengler@opensrcsec.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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