From: syzbot <syzbot+1d9ec4d1a334ae9e1ca6@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: [syzbot] linux-next test error: WARNING in vma_merge
Date: Tue, 24 Jan 2023 01:37:47 -0800 [thread overview]
Message-ID: <000000000000c467c705f2ff449f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a54df7622717 Add linux-next specific files for 20230124
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13220341480000
kernel config: https://syzkaller.appspot.com/x/.config?x=32f13cf65b56e95d
dashboard link: https://syzkaller.appspot.com/bug?extid=1d9ec4d1a334ae9e1ca6
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/131be349f841/disk-a54df762.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/35330c9d8c6e/vmlinux-a54df762.xz
kernel image: https://storage.googleapis.com/syzbot-assets/90c182db9219/bzImage-a54df762.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1d9ec4d1a334ae9e1ca6@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5076 at mm/internal.h:908 vma_iter_store mm/internal.h:908 [inline]
WARNING: CPU: 1 PID: 5076 at mm/internal.h:908 vma_merge.cold+0x2e0/0x6b1 mm/mmap.c:1014
Modules linked in:
CPU: 0 PID: 5076 Comm: syz-fuzzer Not tainted 6.2.0-rc5-next-20230124-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.cold+0x2e0/0x6b1 mm/mmap.c:1014
Code: 2a 48 c1 ea 03 80 3c 02 00 74 09 48 8b 3c 24 e8 7a 39 0f f8 48 8b 04 24 4c 8b 28 e9 e6 4a fe f7 48 89 74 24 48 e8 84 52 c1 f7 <0f> 0b 48 8b 54 24 28 48 c7 c7 a0 60 58 8a 48 8b 74 24 48 e8 e4 d5
RSP: 0018:ffffc90003c5f980 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc90003c5fb60 RCX: 0000000000000000
RDX: ffff88807ec23a80 RSI: ffffffff89c09b9c RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000000000006 R09: 000000c000400000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888077f28d28
R13: ffffc90003c5fb70 R14: ffff888077f28d20 R15: ffffc90003c5fa10
FS: 0000000001f4dab0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0006f3000 CR3: 000000002af6e000 CR4: 00000000003506f0
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/0x20a0 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:00007ffe658ce770 EFLAGS: 00000206 ORIG_RAX: 000000000000001c
RAX: ffffffffffffffda RBX: 0000000000002000 RCX: 00000000004675b7
RDX: 000000000000000f RSI: 0000000000200000 RDI: 000000c000600000
RBP: 00007ffe658ce7b0 R08: 0000000000200000 R09: 0000000000000200
R10: 0000000000000118 R11: 0000000000000206 R12: 00007f77fecbb000
R13: 0000000000000080 R14: 0000000001f4d640 R15: 0000000000001018
</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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2023-01-24 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 9:37 syzbot [this message]
2023-01-24 15:42 ` [syzbot] linux-next test error: WARNING in vma_merge Liam R. Howlett
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=000000000000c467c705f2ff449f@google.com \
--to=syzbot+1d9ec4d1a334ae9e1ca6@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.