[v6.1] WARNING in vma_merge

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b6a09c280000
kernel config: https://syzkaller.appspot.com/x/.config?x=47d3bbfdb3b1ddd2
dashboard link: https://syzkaller.appspot.com/bug?extid=9749096fddfa5953a6a9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/658765c915fa/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d69e8a1aff2d/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0317a9546209/bzImage-ca48fc16.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+974909...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 17705 at mm/mmap.c:1027 vma_merge+0x9a5/0xa30
Modules linked in:
CPU: 0 PID: 17705 Comm: syz-executor.5 Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:vma_merge+0x9a5/0xa30 mm/mmap.c:1027
Code: ff e8 0f 51 bb ff 0f 0b e9 ba fa ff ff e8 03 51 bb ff 0f 0b e9 60 f8 ff ff e8 f7 50 bb ff 0f 0b e9 f6 f9 ff ff e8 eb 50 bb ff <0f> 0b e9 3e fa ff ff e8 df 50 bb ff 0f 0b e9 e4 fb ff ff 48 c7 c1
RSP: 0018:ffffc9000bddfb20 EFLAGS: 00010287
RAX: ffffffff81ce77d5 RBX: 0000000021000000 RCX: 0000000000040000
RDX: ffffc90005d13000 RSI: 0000000000000223 RDI: 0000000000000224
RBP: ffffc9000bddfc10 R08: ffffffff81ce720c R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff888083e8e870
R13: 0000000020a97000 R14: 0000000020ffd000 R15: ffff888058389798
FS: 00007f8db9ebf700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 0000000037259000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
mbind_range+0x3dc/0x790 mm/mempolicy.c:809
do_mbind mm/mempolicy.c:1322 [inline]
kernel_mbind mm/mempolicy.c:1479 [inline]
__do_sys_mbind mm/mempolicy.c:1554 [inline]
__se_sys_mbind+0x792/0xac0 mm/mempolicy.c:1550
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f8db908c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8db9ebf168 EFLAGS: 00000246 ORIG_RAX: 00000000000000ed
RAX: ffffffffffffffda RBX: 00007f8db91abf80 RCX: 00007f8db908c169
RDX: 0000000000000000 RSI: 0000000000c00000 RDI: 0000000020400000
RBP: 00007f8db90e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc2a03e7bf R14: 00007f8db9ebf300 R15: 0000000000022000
</TASK>


---
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 syzk...@googlegroups.com.

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

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

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

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

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14441b64280000
kernel config: https://syzkaller.appspot.com/x/.config?x=aea4bb7802570997

dashboard link: https://syzkaller.appspot.com/bug?extid=9749096fddfa5953a6a9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1127b03c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1215f544280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec11c1903c52/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ce41c1ad391/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/affba5631cad/Image-ca48fc16.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+974909...@syzkaller.appspotmail.com

------------[ cut here ]------------

WARNING: CPU: 0 PID: 4217 at mm/mmap.c:1027 vma_merge+0x9c8/0xb4c mm/mmap.c:1027
Modules linked in:
CPU: 0 PID: 4217 Comm: syz-executor406 Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : vma_merge+0x9c8/0xb4c mm/mmap.c:1027
lr : vma_merge+0x9c8/0xb4c mm/mmap.c:1027
sp : ffff80001d987920
x29: ffff80001d987a10 x28: ffff800015590000 x27: ffff80001d987980
x26: ffff0000c98f4000 x25: 0000000020ffd000 x24: ffff0000c98f4000
x23: 0000000020a97000 x22: dfff800000000000 x21: 0000000021000000
x20: ffff0000c98f4510 x19: 1ffff00002ab20af x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000084f8b64 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000406 x12: ffff70000334acc0
x11: ff808000088714b4 x10: 0000000000000000 x9 : ffff8000088714b4
x8 : ffff0000d58f51c0 x7 : ffff80001208b340 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80001206d32c
x2 : 0000000000000001 x1 : 0000000021000000 x0 : 0000000020a97000
Call trace:
vma_merge+0x9c8/0xb4c mm/mmap.c:1027
mbind_range+0x340/0x6d4 mm/mempolicy.c:809

do_mbind mm/mempolicy.c:1322 [inline]
kernel_mbind mm/mempolicy.c:1479 [inline]
__do_sys_mbind mm/mempolicy.c:1554 [inline]

__se_sys_mbind mm/mempolicy.c:1550 [inline]
__arm64_sys_mbind+0x824/0xaf4 mm/mempolicy.c:1550
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
irq event stamp: 15830
hardirqs last enabled at (15829): [<ffff800008061e04>] local_daif_restore arch/arm64/include/asm/daifflags.h:75 [inline]
hardirqs last enabled at (15829): [<ffff800008061e04>] el0_svc_common+0x9c/0x258 arch/arm64/kernel/syscall.c:107
hardirqs last disabled at (15830): [<ffff8000120e200c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (15816): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (15816): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (15809): [<ffff80000802a948>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ end trace 0000000000000000 ]---


---
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.