BUG: unable to handle kernel paging request in alloc_vmap_area

5 views
Skip to first unread message

syzbot

unread,
Jan 13, 2022, 6:05:29 AM1/13/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=104b07a0700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=87d3df54c57db4d3f231
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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+87d3df...@syzkaller.appspotmail.com

usb usb9: check_ctrlrecip: process 19038 (syz-executor.1) requesting ep 01 but needs 81
usb usb9: usbfs: process 19038 (syz-executor.1) did not claim interface 0 before use
BUG: unable to handle kernel paging request at ffffffffffffffd0
PGD 9e6e067 P4D 9e6e067 PUD 9e70067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 19009 Comm: syz-executor.0 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:alloc_vmap_area+0x342/0x980 mm/vmalloc.c:488
Code: 6d 30 49 81 fd 80 8f 01 8a 0f 84 f3 01 00 00 e8 04 c9 d1 ff 49 8d 6d d0 48 89 e8 48 c1 e8 03 42 80 3c 38 00 0f 85 7f 05 00 00 <4d> 8b 6d d0 4c 89 e7 4c 89 ee e8 ef c9 d1 ff 4d 39 ec 0f 86 c0 01
RSP: 0018:ffff88809fccf908 EFLAGS: 00010246
RAX: 1ffffffffffffffa RBX: ffffc9000b866000 RCX: ffffffff8190bd2a
RDX: 0000000000000000 RSI: ffffffff8190bc6c RDI: ffff888000136bb0
RBP: ffffffffffffffd0 R08: 0000000000000001 R09: ffffc9000b868000
R10: 0000000000000006 R11: 00000000c10dcd7e R12: ffffc9000b868000
R13: 0000000000000000 R14: ffffe8ffffffffff R15: dffffc0000000000
FS: 00007f3dedcca700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd0 CR3: 000000008fb41000 CR4: 00000000003426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__get_vm_area_node+0x17b/0x3a0 mm/vmalloc.c:1401
__vmalloc_node_range mm/vmalloc.c:1748 [inline]
__vmalloc_node mm/vmalloc.c:1804 [inline]
__vmalloc_node_flags mm/vmalloc.c:1818 [inline]
vzalloc+0xe6/0x1a0 mm/vmalloc.c:1857
kvm_dev_ioctl_get_cpuid+0x121/0x6d0 arch/x86/kvm/cpuid.c:813
kvm_arch_dev_ioctl+0x2f8/0x4a0 arch/x86/kvm/x86.c:3165
kvm_dev_ioctl+0xd2/0x16e0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3524
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f3def354c77
Code: 3c 1c 48 f7 d8 49 39 c4 72 b8 e8 04 54 02 00 85 c0 78 bd 48 83 c4 08 4c 89 e0 5b 41 5c c3 0f 1f 44 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3dedcc85d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000020fe8000 RCX: 00007f3def354c77
RDX: 00007f3dedcc8d10 RSI: 00000000c008ae05 RDI: 000000000000001d
RBP: 0000000020fe9000 R08: 0000000000000000 R09: 00000000000000b3
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020fe9800
R13: 00007f3dedcc8d10 R14: 000000000000001d R15: 0000000000000000
Modules linked in:
CR2: ffffffffffffffd0
---[ end trace f563d2e1a312709c ]---
RIP: 0010:alloc_vmap_area+0x342/0x980 mm/vmalloc.c:488
Code: 6d 30 49 81 fd 80 8f 01 8a 0f 84 f3 01 00 00 e8 04 c9 d1 ff 49 8d 6d d0 48 89 e8 48 c1 e8 03 42 80 3c 38 00 0f 85 7f 05 00 00 <4d> 8b 6d d0 4c 89 e7 4c 89 ee e8 ef c9 d1 ff 4d 39 ec 0f 86 c0 01
RSP: 0018:ffff88809fccf908 EFLAGS: 00010246
RAX: 1ffffffffffffffa RBX: ffffc9000b866000 RCX: ffffffff8190bd2a
RDX: 0000000000000000 RSI: ffffffff8190bc6c RDI: ffff888000136bb0
RBP: ffffffffffffffd0 R08: 0000000000000001 R09: ffffc9000b868000
R10: 0000000000000006 R11: 00000000c10dcd7e R12: ffffc9000b868000
R13: 0000000000000000 R14: ffffe8ffffffffff R15: dffffc0000000000
FS: 00007f3dedcca700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd0 CR3: 000000008fb41000 CR4: 00000000003426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 6d insl (%dx),%es:(%rdi)
1: 30 49 81 xor %cl,-0x7f(%rcx)
4: fd std
5: 80 8f 01 8a 0f 84 f3 orb $0xf3,-0x7bf075ff(%rdi)
c: 01 00 add %eax,(%rax)
e: 00 e8 add %ch,%al
10: 04 c9 add $0xc9,%al
12: d1 ff sar %edi
14: 49 8d 6d d0 lea -0x30(%r13),%rbp
18: 48 89 e8 mov %rbp,%rax
1b: 48 c1 e8 03 shr $0x3,%rax
1f: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1)
24: 0f 85 7f 05 00 00 jne 0x5a9
* 2a: 4d 8b 6d d0 mov -0x30(%r13),%r13 <-- trapping instruction
2e: 4c 89 e7 mov %r12,%rdi
31: 4c 89 ee mov %r13,%rsi
34: e8 ef c9 d1 ff callq 0xffd1ca28
39: 4d 39 ec cmp %r13,%r12
3c: 0f .byte 0xf
3d: 86 c0 xchg %al,%al
3f: 01 .byte 0x1


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
May 13, 2022, 7:05:19 AM5/13/22
to syzkaller...@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