[syzbot] [mm?] WARNING in vms_complete_munmap_vmas

From: syzbot
Date: Tue Oct 08 2024 - 16:25:41 EST


Hello,

syzbot found the following issue on:

HEAD commit: 80cb3fb61135 Merge branch 'for-next/core', remote-tracking..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=137aa7d0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9f31443a725c681
dashboard link: https://syzkaller.appspot.com/bug?extid=38c3a8b50658644abaca
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f94327980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177aa7d0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f883f65fbfeb/disk-80cb3fb6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d950aa1c78a2/vmlinux-80cb3fb6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/972c4d758a0b/Image-80cb3fb6.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+38c3a8b50658644abaca@xxxxxxxxxxxxxxxxxxxxxxxxx

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6413 at mm/vma.c:1147 vms_complete_munmap_vmas+0x6f4/0x840 mm/vma.c:1147
Modules linked in:
CPU: 0 UID: 0 PID: 6413 Comm: syz-executor308 Not tainted 6.12.0-rc1-syzkaller-g80cb3fb61135 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : vms_complete_munmap_vmas+0x6f4/0x840 mm/vma.c:1147
lr : vms_complete_munmap_vmas+0x6f4/0x840 mm/vma.c:1147
sp : ffff80009bc27550
x29: ffff80009bc275a0 x28: ffff0000d695f800 x27: 0000000000000c00
x26: ffff0000d695fa00 x25: ffff80009bc277d0 x24: ffff0000d695f9f8
x23: ffff80009bc277c8 x22: 0000000000000021 x21: 00000000000010dd
x20: 1ffff00013784ef6 x19: dfff800000000000 x18: ffff80009bc26b60
x17: 000000000000d6db x16: ffff80008b3bde40 x15: 0000000000000010
x14: 1ffff00013784e84 x13: 0000000000000000 x12: 0000000000000000
x11: ffff700013784e94 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c2c88000 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020
x2 : 0000000000000000 x1 : 0000000000000021 x0 : 0000000000000c00
Call trace:
vms_complete_munmap_vmas+0x6f4/0x840 mm/vma.c:1147
mmap_region+0xc68/0x1e28 mm/mmap.c:1533
do_mmap+0x7e0/0xe00 mm/mmap.c:496
vm_mmap_pgoff+0x1a0/0x38c mm/util.c:588
ksys_mmap_pgoff+0x3f0/0x5c8 mm/mmap.c:542
__do_sys_mmap arch/arm64/kernel/sys.c:28 [inline]
__se_sys_mmap arch/arm64/kernel/sys.c:21 [inline]
__arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:732
el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:750
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
irq event stamp: 8790
hardirqs last enabled at (8789): [<ffff80008047a578>] se


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup