general protection fault in do_swap_page
36 views
Skip to first unread message
syzbot
Jul 6, 2020, 8:43:23 PM7/6/20
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: cd77006e Merge tag 'hyperv-fixes-signed' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1230f755100000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=85c3d44e276759c29481
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+85c3d4...@syzkaller.appspotmail.com
get_swap_device: Bad swap file entry 180099f39ccff380
general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 PID: 15701 Comm: syz-executor.1 Not tainted 5.8.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:do_swap_page+0xdc0/0x2110 mm/memory.c:3127
Code: 10 00 04 00 00 e9 56 f7 ff ff e8 1b 72 d0 ff 48 8b 7c 24 08 e8 91 4c 0a 00 48 ba 00 00 00 00 00 fc ff df 48 89 c1 48 c1 e9 03 <80> 3c 11 00 0f 85 a5 10 00 00 48 8b 18 31 ff 81 e3 00 10 00 00 48
RSP: 0000:ffffc90019737ce0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8880a222f778 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: ffffffff81ad9268 RDI: 0000000000000004
RBP: ffffc90019737dd8 R08: 0000000000000035 R09: ffff8880ae6318e7
R10: 0000000000000000 R11: 0000000000000000 R12: 36cc18c66018fe60
R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000
FS: 0000000001d16940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078bfac CR3: 0000000000092000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
handle_pte_fault mm/memory.c:4229 [inline]
__handle_mm_fault mm/memory.c:4357 [inline]
handle_mm_fault+0x237b/0x43f0 mm/memory.c:4394
do_user_addr_fault+0x5a2/0xd00 arch/x86/mm/fault.c:1295
handle_page_fault arch/x86/mm/fault.c:1365 [inline]
exc_page_fault+0xab/0x170 arch/x86/mm/fault.c:1418
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:565
RIP: 0033:0x4102f7
Code: Bad RIP value.
RSP: 002b:0000000000c9fbf0 EFLAGS: 00010286
RAX: ffffffffffffffff RBX: 000000000000002d RCX: 000000000045cb29
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000078bfac
RBP: 000000000078bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000c9fcd0 R11: 0000000000000246 R12: 00000000000003e8
R13: 00000000001567d1 R14: 00000000001567a4 R15: 000000000078bfac
Modules linked in:
---[ end trace b3a398086ce20370 ]---
RIP: 0010:do_swap_page+0xdc0/0x2110 mm/memory.c:3127
Code: 10 00 04 00 00 e9 56 f7 ff ff e8 1b 72 d0 ff 48 8b 7c 24 08 e8 91 4c 0a 00 48 ba 00 00 00 00 00 fc ff df 48 89 c1 48 c1 e9 03 <80> 3c 11 00 0f 85 a5 10 00 00 48 8b 18 31 ff 81 e3 00 10 00 00 48
RSP: 0000:ffffc90019737ce0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8880a222f778 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: ffffffff81ad9268 RDI: 0000000000000004
RBP: ffffc90019737dd8 R08: 0000000000000035 R09: ffff8880ae6318e7
R10: 0000000000000000 R11: 0000000000000000 R12: 36cc18c66018fe60
R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000
FS: 0000000001d16940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078bfac CR3: 0000000000092000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 found the following crash on:
HEAD commit: cd77006e Merge tag 'hyperv-fixes-signed' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1230f755100000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=85c3d44e276759c29481
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+85c3d4...@syzkaller.appspotmail.com
get_swap_device: Bad swap file entry 180099f39ccff380
general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 PID: 15701 Comm: syz-executor.1 Not tainted 5.8.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:do_swap_page+0xdc0/0x2110 mm/memory.c:3127
Code: 10 00 04 00 00 e9 56 f7 ff ff e8 1b 72 d0 ff 48 8b 7c 24 08 e8 91 4c 0a 00 48 ba 00 00 00 00 00 fc ff df 48 89 c1 48 c1 e9 03 <80> 3c 11 00 0f 85 a5 10 00 00 48 8b 18 31 ff 81 e3 00 10 00 00 48
RSP: 0000:ffffc90019737ce0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8880a222f778 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: ffffffff81ad9268 RDI: 0000000000000004
RBP: ffffc90019737dd8 R08: 0000000000000035 R09: ffff8880ae6318e7
R10: 0000000000000000 R11: 0000000000000000 R12: 36cc18c66018fe60
R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000
FS: 0000000001d16940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078bfac CR3: 0000000000092000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
handle_pte_fault mm/memory.c:4229 [inline]
__handle_mm_fault mm/memory.c:4357 [inline]
handle_mm_fault+0x237b/0x43f0 mm/memory.c:4394
do_user_addr_fault+0x5a2/0xd00 arch/x86/mm/fault.c:1295
handle_page_fault arch/x86/mm/fault.c:1365 [inline]
exc_page_fault+0xab/0x170 arch/x86/mm/fault.c:1418
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:565
RIP: 0033:0x4102f7
Code: Bad RIP value.
RSP: 002b:0000000000c9fbf0 EFLAGS: 00010286
RAX: ffffffffffffffff RBX: 000000000000002d RCX: 000000000045cb29
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000078bfac
RBP: 000000000078bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000c9fcd0 R11: 0000000000000246 R12: 00000000000003e8
R13: 00000000001567d1 R14: 00000000001567a4 R15: 000000000078bfac
Modules linked in:
---[ end trace b3a398086ce20370 ]---
RIP: 0010:do_swap_page+0xdc0/0x2110 mm/memory.c:3127
Code: 10 00 04 00 00 e9 56 f7 ff ff e8 1b 72 d0 ff 48 8b 7c 24 08 e8 91 4c 0a 00 48 ba 00 00 00 00 00 fc ff df 48 89 c1 48 c1 e9 03 <80> 3c 11 00 0f 85 a5 10 00 00 48 8b 18 31 ff 81 e3 00 10 00 00 48
RSP: 0000:ffffc90019737ce0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8880a222f778 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: ffffffff81ad9268 RDI: 0000000000000004
RBP: ffffc90019737dd8 R08: 0000000000000035 R09: ffff8880ae6318e7
R10: 0000000000000000 R11: 0000000000000000 R12: 36cc18c66018fe60
R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000
FS: 0000000001d16940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000078bfac CR3: 0000000000092000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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
Nov 28, 2020, 9:45:15 AM11/28/20
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages