From: syzbot <syzbot+2200e21ff920b6b08faa@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: kernel BUG at mm/huge_memory.c:LINE! (2)
Date: Tue, 08 Sep 2020 06:29:24 -0700 [thread overview]
Message-ID: <000000000000d7327005aecd52f4@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e28f0104 Merge tag 'fixes-2020-09-03' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1252b7fe900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=2200e21ff920b6b08faa
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2200e21ff920b6b08faa@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at mm/huge_memory.c:1654!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 25918 Comm: syz-executor.5 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:zap_huge_pmd+0x8cb/0xfa0 mm/huge_memory.c:1654
Code: 24 1c 0f 84 c9 03 00 00 e8 42 2a bd ff 8b 34 24 bf 1d 00 00 00 e8 b5 26 bd ff 48 83 3c 24 1d 0f 84 ac 03 00 00 e8 25 2a bd ff <0f> 0b e8 1e 2a bd ff 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1
RSP: 0018:ffffc90004ac7730 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0770000000000000 RCX: ffffffff81b720cb
RDX: ffff8880985c0200 RSI: ffffffff81b720db RDI: 0000000000000005
RBP: ffffc90004ac7a50 R08: 0000000000000001 R09: ffff888000183827
R10: 000000000000001d R11: 0000000000000000 R12: ffff888000183820
R13: ffff88804d29b900 R14: ffffffff89b63d70 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a3b73 CR3: 000000009b476000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
zap_pmd_range mm/memory.c:1182 [inline]
zap_pud_range mm/memory.c:1224 [inline]
zap_p4d_range mm/memory.c:1245 [inline]
unmap_page_range+0x107b/0x2b20 mm/memory.c:1266
unmap_single_vma+0x198/0x300 mm/memory.c:1311
unmap_vmas+0x168/0x2e0 mm/memory.c:1343
exit_mmap+0x2b1/0x530 mm/mmap.c:3183
__mmput+0x122/0x470 kernel/fork.c:1076
mmput+0x53/0x60 kernel/fork.c:1097
exit_mm kernel/exit.c:483 [inline]
do_exit+0xa8b/0x29f0 kernel/exit.c:793
do_group_exit+0x125/0x310 kernel/exit.c:903
get_signal+0x428/0x1f00 kernel/signal.c:2757
arch_do_signal+0x82/0x2520 arch/x86/kernel/signal.c:811
exit_to_user_mode_loop kernel/entry/common.c:136 [inline]
exit_to_user_mode_prepare+0x1ae/0x200 kernel/entry/common.c:167
syscall_exit_to_user_mode+0x7e/0x2e0 kernel/entry/common.c:242
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5b9
Code: Bad RIP value.
RSP: 002b:00007f290f37fcf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 000000000118cfe8 RCX: 000000000045d5b9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 000000000118cfec
RBP: 000000000118cfe0 R08: 000000000000000e R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cfec
R13: 00007ffc935c909f R14: 00007f290f3809c0 R15: 000000000118cfec
Modules linked in:
---[ end trace 9c85984f4836a6e7 ]---
RIP: 0010:zap_huge_pmd+0x8cb/0xfa0 mm/huge_memory.c:1654
Code: 24 1c 0f 84 c9 03 00 00 e8 42 2a bd ff 8b 34 24 bf 1d 00 00 00 e8 b5 26 bd ff 48 83 3c 24 1d 0f 84 ac 03 00 00 e8 25 2a bd ff <0f> 0b e8 1e 2a bd ff 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1
RSP: 0018:ffffc90004ac7730 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0770000000000000 RCX: ffffffff81b720cb
RDX: ffff8880985c0200 RSI: ffffffff81b720db RDI: 0000000000000005
RBP: ffffc90004ac7a50 R08: 0000000000000001 R09: ffff888000183827
R10: 000000000000001d R11: 0000000000000000 R12: ffff888000183820
R13: ffff88804d29b900 R14: ffffffff89b63d70 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a3b73 CR3: 000000009b476000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
reply other threads:[~2020-09-08 13:29 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=000000000000d7327005aecd52f4@google.com \
--to=syzbot+2200e21ff920b6b08faa@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.