From: syzbot <syzbot+52343d77314d6c0447fe@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, david@redhat.com,
harry.yoo@oracle.com, jannh@google.com, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, pfalcato@suse.de, riel@surriel.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] WARNING: bad unlock balance in move_pgt_entry
Date: Tue, 17 Jun 2025 22:07:04 -0700 [thread overview]
Message-ID: <68524978.050a0220.2608ac.002a.GAE@google.com> (raw)
In-Reply-To: <68512333.a70a0220.395abc.0205.GAE@google.com>
syzbot has bisected this issue to:
commit aaf5c23bf6a474f11f48f03bd6a9b551f4e7d45a
Author: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Date: Mon Jun 9 13:26:35 2025 +0000
mm/mremap: introduce more mergeable mremap via MREMAP_RELOCATE_ANON
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11f92370580000
start commit: 050f8ad7b58d Add linux-next specific files for 20250616
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13f92370580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15f92370580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2efc7740224b93a
dashboard link: https://syzkaller.appspot.com/bug?extid=52343d77314d6c0447fe
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11389e82580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16824370580000
Reported-by: syzbot+52343d77314d6c0447fe@syzkaller.appspotmail.com
Fixes: aaf5c23bf6a4 ("mm/mremap: introduce more mergeable mremap via MREMAP_RELOCATE_ANON")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-18 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 8:11 syzbot
2025-06-17 19:45 ` Lorenzo Stoakes
2025-06-18 5:07 ` 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=68524978.050a0220.2608ac.002a.GAE@google.com \
--to=syzbot+52343d77314d6c0447fe@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.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=riel@surriel.com \
--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