BUG: unable to handle kernel paging request in clear_page_erms (3)

9 visningar
Hoppa till det första olästa meddelandet

syzbot

oläst,
5 juli 2021 06:10:162021-07-05
till syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: dbe69e43 Merge tag 'net-next-5.14' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a34718300000
kernel config: https://syzkaller.appspot.com/x/.config?x=47e4697be2f5b985
dashboard link: https://syzkaller.appspot.com/bug?extid=ee977076aeb6b7f75e4c
userspace arch: i386
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

BUG: unable to handle page fault for address: ffff8881521be000
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 10e01067 P4D 10e01067 PUD 14d75a063 PMD 10e063 PTE 8000000100000000
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8983 Comm: syz-executor.5 Tainted: G W 5.13.0-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:49
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 cc cc cc cc cc cc 41 57 41 56 41 55 41 54 55 53 48 89 fb
RSP: 0018:ffffc9000175f600 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffea0005486f80 RCX: 0000000000001000
RDX: 1ffff11005912605 RSI: 0000000000000001 RDI: ffff8881521be000
RBP: ffff88802c891c40 R08: 0000000000000001 R09: ffffed102a437c00
R10: fffff94000a90df6 R11: 0000000000000000 R12: ffffed1005912659
R13: dffffc0000000000 R14: ffffea0005486fc0 R15: ffff88802c8932c8
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0063) knlGS:000000000aa0b380
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: ffff8881521be000 CR3: 000000005da08000 CR4: 00000000001526e0
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:184 [inline]
kernel_init_free_pages.part.0+0x99/0x120 mm/page_alloc.c:1295
kernel_init_free_pages mm/page_alloc.c:1284 [inline]
post_alloc_hook+0x145/0x1e0 mm/page_alloc.c:2435
prep_new_page mm/page_alloc.c:2445 [inline]
get_page_from_freelist+0xa72/0x2f80 mm/page_alloc.c:4178
__alloc_pages+0x1b2/0x500 mm/page_alloc.c:5386
alloc_pages+0x18c/0x2a0 mm/mempolicy.c:2272
__get_free_pages+0x8/0x40 mm/page_alloc.c:5423
_pgd_alloc arch/x86/mm/pgtable.c:414 [inline]
pgd_alloc+0x81/0x360 arch/x86/mm/pgtable.c:430
mm_alloc_pgd kernel/fork.c:628 [inline]
mm_init+0x5fd/0xaa0 kernel/fork.c:1062
dup_mm+0xd8/0x1380 kernel/fork.c:1376
copy_mm kernel/fork.c:1431 [inline]
copy_process+0x71e0/0x74c0 kernel/fork.c:2119
kernel_clone+0xe7/0xab0 kernel/fork.c:2509
__do_compat_sys_ia32_clone+0xac/0xe0 arch/x86/kernel/sys_ia32.c:254
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178
do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:203
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
RIP: 0023:0xf7fe8549
Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000086cfd30 EFLAGS: 00000206 ORIG_RAX: 0000000000000078
RAX: ffffffffffffffda RBX: 0000000001200011 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000aa0b3e8
RBP: 000000000816c000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: ffff8881521be000
---[ end trace 7bf52661da1076d8 ]---
RIP: 0010:clear_page_erms+0x7/0x10 arch/x86/lib/clear_page_64.S:49
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 cc cc cc cc cc cc 41 57 41 56 41 55 41 54 55 53 48 89 fb
RSP: 0018:ffffc9000175f600 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffea0005486f80 RCX: 0000000000001000
RDX: 1ffff11005912605 RSI: 0000000000000001 RDI: ffff8881521be000
RBP: ffff88802c891c40 R08: 0000000000000001 R09: ffffed102a437c00
R10: fffff94000a90df6 R11: 0000000000000000 R12: ffffed1005912659
R13: dffffc0000000000 R14: ffffea0005486fc0 R15: ffff88802c8932c8
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0063) knlGS:000000000aa0b380
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: ffff8881521be000 CR3: 000000005da08000 CR4: 00000000001526e0
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 syzk...@googlegroups.com.

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

syzbot

oläst,
9 okt. 2021 17:56:112021-10-09
till syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Svara alla
Svara författaren
Vidarebefordra
0 nya meddelanden