BUG: unable to handle kernel paging request in migration_entry_to_page

13 views
Skip to first unread message

syzbot

unread,
Sep 27, 2018, 3:14:04 PM9/27/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 6bf4ca7fbc85 Linux 4.19-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1053703a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=22a62640793a83c9
dashboard link: https://syzkaller.appspot.com/bug?extid=cc120482faedfd711b7f
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ak...@linux-foundation.org dan.j.w...@intel.com
dw...@amazon.co.uk jrdr....@gmail.com linux-...@vger.kernel.org
linu...@kvack.org li...@dominikbrodowski.net mho...@suse.com
rien...@google.com]

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

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

BUG: unable to handle kernel paging request at ffffea000edfb988
PGD 2187ef067 P4D 2187ef067 PUD 2187ee067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 21235 Comm: syz-executor5 Not tainted 4.19.0-rc5+ #30
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline]
RIP: 0010:compound_head include/linux/page-flags.h:142 [inline]
RIP: 0010:migration_entry_to_page+0x106/0x550 include/linux/swapops.h:215
Code: 06 48 01 c3 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 08 48 89 fa 48 c1
ea 03 80 3c 02 00 0f 85 69 03 00 00 4d 8d a6 40 ff ff ff <4c> 8b 7b 08 48
b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 80
RSP: 0018:ffff88019a4f6ae0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffea000edfb980 RCX: ffffffff81b21a8f
RDX: 1ffffd4001dbf731 RSI: ffffffff81b17c76 RDI: ffffea000edfb988
RBP: ffff88019a4f6c38 R08: ffff8801bf0fa000 R09: fffff94000de277e
R10: fffff94000de277e R11: ffffea0006f13bf3 R12: ffff88019a4f6b50
R13: 1ffff1003349ed5e R14: ffff88019a4f6c10 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8801dac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffea000edfb988 CR3: 0000000131780000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
zap_pte_range mm/memory.c:1381 [inline]
zap_pmd_range mm/memory.c:1440 [inline]
zap_pud_range mm/memory.c:1469 [inline]
zap_p4d_range mm/memory.c:1490 [inline]
unmap_page_range+0x10e6/0x2030 mm/memory.c:1511
unmap_single_vma+0x19b/0x310 mm/memory.c:1556
unmap_vmas+0x125/0x200 mm/memory.c:1586
exit_mmap+0x2be/0x590 mm/mmap.c:3093
__mmput kernel/fork.c:1001 [inline]
mmput+0x247/0x610 kernel/fork.c:1022
exit_mm kernel/exit.c:545 [inline]
do_exit+0xe6f/0x2610 kernel/exit.c:854
do_group_exit+0x177/0x440 kernel/exit.c:970
get_signal+0x8b0/0x1980 kernel/signal.c:2513
do_signal+0x9c/0x21e0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2e5/0x380 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457679
Code: Bad RIP value.
RSP: 002b:00007f046a5d9cf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000072bf08 RCX: 0000000000457679
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000072bf08
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000072bf0c
R13: 00007ffcf4d4e36f R14: 00007f046a5da9c0 R15: 0000000000000000
Modules linked in:
CR2: ffffea000edfb988
---[ end trace d4979d8d9531af1f ]---
RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline]
RIP: 0010:compound_head include/linux/page-flags.h:142 [inline]
RIP: 0010:migration_entry_to_page+0x106/0x550 include/linux/swapops.h:215
Code: 06 48 01 c3 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 08 48 89 fa 48 c1
ea 03 80 3c 02 00 0f 85 69 03 00 00 4d 8d a6 40 ff ff ff <4c> 8b 7b 08 48
b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 80
RSP: 0018:ffff88019a4f6ae0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffea000edfb980 RCX: ffffffff81b21a8f
RDX: 1ffffd4001dbf731 RSI: ffffffff81b17c76 RDI: ffffea000edfb988
RBP: ffff88019a4f6c38 R08: ffff8801bf0fa000 R09: fffff94000de277e
R10: fffff94000de277e R11: ffffea0006f13bf3 R12: ffff88019a4f6b50
R13: 1ffff1003349ed5e R14: ffff88019a4f6c10 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8801dac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000045764f CR3: 0000000131780000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Mar 23, 2019, 6:58:06 AM3/23/19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages