syzbot


linux-next test error: WARNING in vma_merge

Status: upstream: reported on 2023/01/24 09:37
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+1d9ec4d1a334ae9e1ca6@syzkaller.appspotmail.com
Fix commit: mm/madvise: fix VMA_ITERATOR start position
Patched on: [ci-upstream-linux-next-kasan-gce-root], missing on: [ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-qemu2-riscv64 ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-badwrites-root ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce-386-root ci-upstream-kmsan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-net-next-test-gce ci2-upstream-usb]
First crash: 450d, last: 449d
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] mm/madvise: Fix VMA_ITERATOR start position 1 (1) 2023/01/25 13:58
[syzbot] linux-next test error: WARNING in vma_merge 1 (2) 2023/01/24 15:42

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5079 at mm/internal.h:908 vma_iter_store mm/internal.h:908 [inline]
WARNING: CPU: 0 PID: 5079 at mm/internal.h:908 vma_merge+0x6ab/0x20a0 mm/mmap.c:1014
Modules linked in:
CPU: 0 PID: 5079 Comm: syz-fuzzer Not tainted 6.2.0-rc5-next-20230125-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:vma_iter_store mm/internal.h:908 [inline]
RIP: 0010:vma_merge+0x6ab/0x20a0 mm/mmap.c:1014
Code: 24 28 48 8b 70 10 48 89 74 24 48 e8 3f 9d c2 ff 48 8b 74 24 48 48 39 74 24 28 0f 86 3e 01 00 00 48 89 74 24 48 e8 e5 a0 c2 ff <0f> 0b 48 8b 54 24 28 48 c7 c7 a0 5f 58 8a 48 8b 74 24 48 e8 fd 80
RSP: 0018:ffffc90003d0f980 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc90003d0fb68 RCX: 0000000000000000
RDX: ffff88802047d7c0 RSI: ffffffff81c20c2b RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000000000006 R09: 000000c000400000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88802a6b70e8
R13: ffffc90003d0fb70 R14: ffff88802a6b70e0 R15: ffffc90003d0fa10
FS:  0000000001f4dab0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000019bcf50 CR3: 000000001cd36000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 madvise_update_vma+0x21b/0xa80 mm/madvise.c:153
 madvise_vma_behavior+0x7ea/0x20c0 mm/madvise.c:1091
 madvise_walk_vmas+0x1c7/0x2b0 mm/madvise.c:1260
 do_madvise.part.0+0x18e/0x340 mm/madvise.c:1439
 do_madvise mm/madvise.c:1452 [inline]
 __do_sys_madvise mm/madvise.c:1452 [inline]
 __se_sys_madvise mm/madvise.c:1450 [inline]
 __x64_sys_madvise+0x117/0x150 mm/madvise.c:1450
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x4675b7
Code: 8b 24 24 48 8b 6c 24 10 48 83 c4 18 c3 cc cc cc cc cc cc 48 8b 7c 24 08 48 8b 74 24 10 8b 54 24 18 48 c7 c0 1c 00 00 00 0f 05 <89> 44 24 20 c3 cc cc cc cc 48 8b 7c 24 08 8b 74 24 10 8b 54 24 14
RSP: 002b:00007ffdb2dd67b0 EFLAGS: 00000206 ORIG_RAX: 000000000000001c
RAX: ffffffffffffffda RBX: 0000000000002000 RCX: 00000000004675b7
RDX: 000000000000000f RSI: 0000000000200000 RDI: 000000c000600000
RBP: 00007ffdb2dd67f0 R08: 0000000000200000 R09: 0000000000000200
R10: 0000000000000123 R11: 0000000000000206 R12: 00007fc72e285000
R13: 0000000000000080 R14: 0000000001f4d640 R15: 0000000000001018
 </TASK>

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/25 04:31 linux-next 9fbee811e479 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
2023/01/25 04:30 linux-next 9fbee811e479 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
2023/01/25 04:30 linux-next 9fbee811e479 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
2023/01/24 04:20 linux-next a54df7622717 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
2023/01/24 04:20 linux-next a54df7622717 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
2023/01/24 04:20 linux-next a54df7622717 9dfcf09c .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next test error: WARNING in vma_merge
* Struck through repros no longer work on HEAD.