BUG: unable to handle kernel paging request in clear_page_erms

17 views
Skip to first unread message

syzbot

unread,
Jan 4, 2022, 5:20:18 PM1/4/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=14c9441db00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=02799d7c09f278459861
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+02799d...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at ffff888238222000
PGD de01067 P4D de01067 PUD 30063 PMD 1c7063 PTE 8000000200077000
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3211 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:clear_page_erms+0x7/0x10 arch/x86/lib/clear_page_64.S:48
Code: 48 89 47 18 48 89 47 20 48 89 47 28 48 89 47 30 48 89 47 38 48 8d 7f 40 75 d9 90 c3 0f 1f 80 00 00 00 00 b9 00 10 00 00 31 c0 <f3> aa c3 90 90 90 90 90 90 41 57 41 56 41 55 41 54 55 53 48 89 fb
RSP: 0000:ffff8882363df7a0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888094ead8f8 RCX: 0000000000001000
RDX: 1ffff110129d5aef RSI: ffffea0008e08880 RDI: ffff888238222000
RBP: ffffea0008e08880 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffed10129d5b1f
R13: ffff888094eac540 R14: dffffc0000000000 R15: dffffc0000000000
FS: 00005555561f6400(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888238222000 CR3: 0000000000a48000 CR4: 00000000003426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
clear_page arch/x86/include/asm/page_64.h:49 [inline]
clear_highpage include/linux/highmem.h:190 [inline]
prep_new_page mm/page_alloc.c:1949 [inline]
get_page_from_freelist+0x1f22/0x4170 mm/page_alloc.c:3376
__alloc_pages_nodemask+0x387/0x2890 mm/page_alloc.c:4399
alloc_pages_current+0x193/0x2a0 mm/mempolicy.c:2197
alloc_pages include/linux/gfp.h:532 [inline]
pte_alloc_one+0x16/0x190 arch/x86/mm/pgtable.c:35
__pte_alloc+0x21/0x340 mm/memory.c:665
do_anonymous_page+0xff4/0x1be0 mm/memory.c:3282
handle_pte_fault mm/memory.c:4173 [inline]
__handle_mm_fault+0x227a/0x41c0 mm/memory.c:4299
handle_mm_fault+0x436/0xb10 mm/memory.c:4336
__do_page_fault+0x68e/0xd60 arch/x86/mm/fault.c:1412
page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1205
RIP: 0033:0x7fe9482fd07a
Code: 30 48 8b 34 24 48 85 f6 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fe 01 0f 85 a1 01 00 00 48 8b 44 24 10 8b 74 24 18 <89> 30 e9 d2 fc ff ff 48 8b 44 24 10 8b 10 48 8b 04 24 48 85 c0 0f
RSP: 002b:00007ffe50e9a6f0 EFLAGS: 00010246
RAX: 0000000020000100 RBX: 0000000000000000 RCX: 0000000000000000
RDX: b3783505af765b79 RSI: 0000000000000001 RDI: 00005555561f62f0
RBP: 00007ffe50e9a7e8 R08: 0000000000000000 R09: 0000000000000000
R10: 001307fdfd35b942 R11: 0000000000000001 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007ffe50e9a9d0
Modules linked in:
CR2: ffff888238222000
---[ end trace a7882cec6ce0fa85 ]---
RIP: 0010:clear_page_erms+0x7/0x10 arch/x86/lib/clear_page_64.S:48
Code: 48 89 47 18 48 89 47 20 48 89 47 28 48 89 47 30 48 89 47 38 48 8d 7f 40 75 d9 90 c3 0f 1f 80 00 00 00 00 b9 00 10 00 00 31 c0 <f3> aa c3 90 90 90 90 90 90 41 57 41 56 41 55 41 54 55 53 48 89 fb
RSP: 0000:ffff8882363df7a0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888094ead8f8 RCX: 0000000000001000
RDX: 1ffff110129d5aef RSI: ffffea0008e08880 RDI: ffff888238222000
RBP: ffffea0008e08880 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffed10129d5b1f
R13: ffff888094eac540 R14: dffffc0000000000 R15: dffffc0000000000
FS: 00005555561f6400(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888238222000 CR3: 0000000000a48000 CR4: 00000000003426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 48 89 47 18 mov %rax,0x18(%rdi)
4: 48 89 47 20 mov %rax,0x20(%rdi)
8: 48 89 47 28 mov %rax,0x28(%rdi)
c: 48 89 47 30 mov %rax,0x30(%rdi)
10: 48 89 47 38 mov %rax,0x38(%rdi)
14: 48 8d 7f 40 lea 0x40(%rdi),%rdi
18: 75 d9 jne 0xfffffff3
1a: 90 nop
1b: c3 retq
1c: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
23: b9 00 10 00 00 mov $0x1000,%ecx
28: 31 c0 xor %eax,%eax
* 2a: f3 aa rep stos %al,%es:(%rdi) <-- trapping instruction
2c: c3 retq
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 90 nop
31: 90 nop
32: 90 nop
33: 41 57 push %r15
35: 41 56 push %r14
37: 41 55 push %r13
39: 41 54 push %r12
3b: 55 push %rbp
3c: 53 push %rbx
3d: 48 89 fb mov %rdi,%rbx


---
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 4, 2022, 6:20:17 PM5/4/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