WARNING in unmap_single_vma

6 views
Skip to first unread message

syzbot

unread,
Aug 23, 2019, 9:21:07 AM8/23/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 45f092f9 Linux 4.14.139
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12991b0e600000
kernel config: https://syzkaller.appspot.com/x/.config?x=56ab4cf14cc8892d
dashboard link: https://syzkaller.appspot.com/bug?extid=701d4b51fdc3355fe2b9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16dac2ca600000

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

should_failslab+0xdb/0x130 mm/failslab.c:32
slab_pre_alloc_hook mm/slab.h:421 [inline]
slab_alloc mm/slab.c:3376 [inline]
kmem_cache_alloc+0x2d7/0x780 mm/slab.c:3550
ptlock_alloc+0x20/0x70 mm/memory.c:4741
------------[ cut here ]------------
ptlock_init include/linux/mm.h:1757 [inline]
pgtable_page_ctor include/linux/mm.h:1791 [inline]
pte_alloc_one+0x60/0x100 arch/x86/mm/pgtable.c:33
WARNING: CPU: 0 PID: 6742 at arch/x86/mm/pat.c:1020 untrack_pfn+0x1dc/0x220
arch/x86/mm/pat.c:1020
__pte_alloc+0x2a/0x2d0 mm/memory.c:656
Kernel panic - not syncing: panic_on_warn set ...

copy_pte_range mm/memory.c:1081 [inline]
copy_pmd_range mm/memory.c:1157 [inline]
copy_pud_range mm/memory.c:1191 [inline]
copy_p4d_range mm/memory.c:1213 [inline]
copy_page_range+0x11ba/0x1bd0 mm/memory.c:1275
dup_mmap kernel/fork.c:714 [inline]
dup_mm kernel/fork.c:1208 [inline]
copy_mm kernel/fork.c:1263 [inline]
copy_process.part.0+0x4764/0x6a00 kernel/fork.c:1780
copy_process kernel/fork.c:1595 [inline]
_do_fork+0x19e/0xce0 kernel/fork.c:2085
SYSC_clone kernel/fork.c:2195 [inline]
SyS_clone+0x37/0x50 kernel/fork.c:2189
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x459829
RSP: 002b:00007f768a0f8c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f768a0f8c90 RCX: 0000000000459829
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f768a0f96d4
R13: 00000000004bfce6 R14: 00000000004d1a58 R15: 0000000000000005
CPU: 0 PID: 6742 Comm: syz-executor.1 Not tainted 4.14.139 #35
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x138/0x19c lib/dump_stack.c:53
panic+0x1f2/0x426 kernel/panic.c:182
__warn.cold+0x2f/0x36 kernel/panic.c:546
report_bug+0x216/0x254 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x1bb/0x310 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:untrack_pfn+0x1dc/0x220 arch/x86/mm/pat.c:1020
RSP: 0018:ffff8880925ef948 EFLAGS: 00010297
RAX: ffff88808a88e3c0 RBX: ffff8880956bada8 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffff8880925ef9d8 R08: ffff88808a88e3c0 R09: 0000000000000000
R10: 0000000000000000 R11: ffff88808a88e3c0 R12: 1ffff110124bdf2a
R13: 0000000000000000 R14: 0000000000000000 R15: ffff8880925ef9b0
unmap_single_vma+0x182/0x2c0 mm/memory.c:1539
unmap_vmas+0xac/0x170 mm/memory.c:1590
exit_mmap+0x285/0x4e0 mm/mmap.c:3062
__mmput kernel/fork.c:935 [inline]
mmput+0x114/0x440 kernel/fork.c:956
dup_mm kernel/fork.c:1224 [inline]
copy_mm kernel/fork.c:1263 [inline]
copy_process.part.0+0x4743/0x6a00 kernel/fork.c:1780
copy_process kernel/fork.c:1595 [inline]
_do_fork+0x19e/0xce0 kernel/fork.c:2085
SYSC_clone kernel/fork.c:2195 [inline]
SyS_clone+0x37/0x50 kernel/fork.c:2189
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x459829
RSP: 002b:00007f37d3880c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f37d3880c90 RCX: 0000000000459829
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f37d38816d4
R13: 00000000004bfce6 R14: 00000000004d1a58 R15: 0000000000000005
CPU: 1 PID: 6749 Comm: syz-executor.5 Not tainted 4.14.139 #35
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x138/0x19c lib/dump_stack.c:53
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0x10f/0x159 lib/fault-inject.c:149
should_failslab+0xdb/0x130 mm/failslab.c:32
slab_pre_alloc_hook mm/slab.h:421 [inline]
slab_alloc mm/slab.c:3376 [inline]
kmem_cache_alloc+0x2d7/0x780 mm/slab.c:3550
dup_mmap kernel/fork.c:652 [inline]
dup_mm kernel/fork.c:1208 [inline]
copy_mm kernel/fork.c:1263 [inline]
copy_process.part.0+0x444f/0x6a00 kernel/fork.c:1780
copy_process kernel/fork.c:1595 [inline]
_do_fork+0x19e/0xce0 kernel/fork.c:2085
SYSC_clone kernel/fork.c:2195 [inline]
SyS_clone+0x37/0x50 kernel/fork.c:2189
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x459829
RSP: 002b:00007f5de3de9c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f5de3de9c90 RCX: 0000000000459829
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5de3dea6d4
R13: 00000000004bfce6 R14: 00000000004d1a58 R15: 0000000000000005
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages