From: syzbot <syzbot+a85a0b4b0f39dca529a5@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [mm?] WARNING in validate_mm
Date: Wed, 05 Jul 2023 15:38:09 -0700 [thread overview]
Message-ID: <000000000000dc3ea105ffc50d00@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14aeea08a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d787595a482d6a43
dashboard link: https://syzkaller.appspot.com/bug?extid=a85a0b4b0f39dca529a5
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/9f5f0447f626/disk-a901a356.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/500177760bfb/vmlinux-a901a356.xz
kernel image: https://storage.googleapis.com/syzbot-assets/82352cc74fb3/bzImage-a901a356.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a85a0b4b0f39dca529a5@syzkaller.appspotmail.com
owner ffff88807cee5940 exe_file ffff888028ce6f00
notifier_subscriptions 0000000000000000
numa_next_scan 4295297648 numa_scan_offset 0 numa_scan_seq 0
tlb_flush_pending 1
def_flags: 0x0()
------------[ cut here ]------------
WARNING: CPU: 0 PID: 18358 at mm/mmap.c:314 validate_mm+0x42a/0x500 mm/mmap.c:314
Modules linked in:
CPU: 0 PID: 18358 Comm: syz-executor.2 Not tainted 6.4.0-syzkaller-10173-ga901a3568fd2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:validate_mm+0x42a/0x500 mm/mmap.c:314
Code: 28 e8 5a 98 fa ff c6 05 96 e3 b0 0c 01 0f 0b e9 09 fe ff ff e8 77 e1 b9 ff 48 8b 7c 24 28 e8 3d 98 fa ff c6 05 7a e3 b0 0c 01 <0f> 0b e9 46 ff ff ff e8 5a e1 b9 ff 44 8b 74 24 1c eb 08 e8 4e e1
RSP: 0018:ffffc90006a279a0 EFLAGS: 00010282
RAX: 0000000000000330 RBX: 0000000000000000 RCX: 3ddfd82186994a00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90006a27ad0 R08: ffffffff816f481c R09: 1ffff92000d44e5c
R10: dffffc0000000000 R11: fffff52000d44e5d R12: dffffc0000000000
R13: ffffc90006a27a20 R14: ffff888024681500 R15: 00007f2d1ec14000
FS: 00007f2d1ec97700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f690424b000 CR3: 000000001ebc5000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
do_vmi_align_munmap+0x13b1/0x15c0 mm/mmap.c:2561
do_vmi_munmap+0x24d/0x2d0 mm/mmap.c:2619
__vm_munmap+0x230/0x450 mm/mmap.c:2899
__do_sys_munmap mm/mmap.c:2916 [inline]
__se_sys_munmap mm/mmap.c:2913 [inline]
__x64_sys_munmap+0x69/0x80 mm/mmap.c:2913
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f2d1de8c467
Code: 00 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb 85 66 2e 0f 1f 84 00 00 00 00 00 90 b8 0b 00 00 00 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:00007f2d1ec96f38 EFLAGS: 00000246 ORIG_RAX: 000000000000000b
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f2d1de8c467
RDX: 0000000000010000 RSI: 0000000000010000 RDI: 00007f2d145ff000
RBP: 00007f2d145ff000 R08: 0000000000000000 R09: 000000000000028b
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2d1ec96fdc R14: 00007f2d1ec96fe0 R15: 0000000020000382
</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.
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
reply other threads:[~2023-07-05 22:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000dc3ea105ffc50d00@google.com \
--to=syzbot+a85a0b4b0f39dca529a5@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.