BUG: unable to handle kernel paging request in __handle_mm_fault (2)

6 views
Skip to first unread message

syzbot

unread,
May 17, 2021, 7:40:23 AM5/17/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e3d35712 Add linux-next specific files for 20210423
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15aadf15d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e370221d7500b26a
dashboard link: https://syzkaller.appspot.com/bug?extid=0c01c78b1f433d38d892
CC: [ak...@linux-foundation.org b...@alien8.de h...@zytor.com linux-...@vger.kernel.org mi...@redhat.com nive...@alum.mit.edu pet...@infradead.org tg...@linutronix.de wei...@kernel.org x...@kernel.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+0c01c7...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffffef2c1ffffc00
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8438 Comm: syz-fuzzer Not tainted 5.12.0-rc8-next-20210423-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:native_pud_val arch/x86/include/asm/pgtable_types.h:366 [inline]
RIP: 0010:pud_none arch/x86/include/asm/pgtable.h:860 [inline]
RIP: 0010:__handle_mm_fault+0x341/0x5150 mm/memory.c:4441
Code: c8 8d 48 c1 e8 03 4c 01 f0 48 89 04 24 48 8b 44 24 40 48 c1 e8 03 4c 01 f0 48 89 44 24 28 e8 e6 42 cb ff 48 89 e8 48 c1 e8 03 <42> 80 3c 30 00 0f 85 37 1f 00 00 48 8b 6d 00 48 8b 04 24 49 89 ec
RSP: 0000:ffffc90000eafd00 EFLAGS: 00010a06
RAX: 1ffff32c1ffffc00 RBX: ffff888000000000 RCX: 0000000000000000
RDX: ffff8880125f8000 RSI: ffffffff81a9b68a RDI: 0000000000000003
RBP: ffff9960ffffe000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81a9b62d R11: 0000000000000000 R12: 0000000000000000
R13: 000010e0ffffe000 R14: dffffc0000000000 R15: ffff8880129c4000
FS: 000000c00002e090(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffef2c1ffffc00 CR3: 000000002f848000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
handle_mm_fault+0x1bc/0x7e0 mm/memory.c:4600
do_user_addr_fault+0x483/0x1210 arch/x86/mm/fault.c:1390
handle_page_fault arch/x86/mm/fault.c:1475 [inline]
exc_page_fault+0x9e/0x180 arch/x86/mm/fault.c:1531
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:577
RIP: 0033:0x46dabd
Code: Unable to access opcode bytes at RIP 0x46da93.
RSP: 002b:000000c00003df18 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000014 RCX: 000000000046dabd
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000c00003df18
RBP: 000000c00003df28 R08: 00000000000008a0 R09: 00007ffe39924080
R10: 00007ffe39924090 R11: 0000000000000202 R12: 000000000043b6a0
R13: 0000000000000000 R14: 0000000000947a14 R15: 0000000000000000
Modules linked in:
CR2: ffffef2c1ffffc00
---[ end trace 95c475e9709e19fa ]---
RIP: 0010:native_pud_val arch/x86/include/asm/pgtable_types.h:366 [inline]
RIP: 0010:pud_none arch/x86/include/asm/pgtable.h:860 [inline]
RIP: 0010:__handle_mm_fault+0x341/0x5150 mm/memory.c:4441
Code: c8 8d 48 c1 e8 03 4c 01 f0 48 89 04 24 48 8b 44 24 40 48 c1 e8 03 4c 01 f0 48 89 44 24 28 e8 e6 42 cb ff 48 89 e8 48 c1 e8 03 <42> 80 3c 30 00 0f 85 37 1f 00 00 48 8b 6d 00 48 8b 04 24 49 89 ec
RSP: 0000:ffffc90000eafd00 EFLAGS: 00010a06
RAX: 1ffff32c1ffffc00 RBX: ffff888000000000 RCX: 0000000000000000
RDX: ffff8880125f8000 RSI: ffffffff81a9b68a RDI: 0000000000000003
RBP: ffff9960ffffe000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81a9b62d R11: 0000000000000000 R12: 0000000000000000
R13: 000010e0ffffe000 R14: dffffc0000000000 R15: ffff8880129c4000
FS: 000000c00002e090(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000046da93 CR3: 000000002f848000 CR4: 00000000001506f0
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

unread,
Jun 28, 2021, 3:59:15 PM6/28/21
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