invalid opcode in do_fast_syscall_32
8 views
Skip to first unread message
syzbot
Jan 7, 2020, 4:14:11 PM1/7/20
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: bed72351 Merge tag 'kbuild-fixes-v5.5-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e459c1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=874bac2ff63646fa
dashboard link: https://syzkaller.appspot.com/bug?extid=6dc4f484e2c2106c429b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: i386
CC: [b...@alien8.de h...@zytor.com linux-...@vger.kernel.org
lu...@kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.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+6dc4f4...@syzkaller.appspotmail.com
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9336 Comm: syz-executor.5 Not tainted 5.5.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:do_fast_syscall_32+0x760/0xe16 arch/x86/entry/common.c:422
Code: 0f 85 5e 06 00 00 49 8b 9c 24 80 00 00 00 4c 89 ee 45 31 f6 48 89 df
e8 ee 72 74 00 4c 39 eb 0f 85 78 fe ff ff e8 c0 71 74 00 <07> 07 07 07 07
07 07 07 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0018:ffffc90001fa7f10 EFLAGS: 00010093
RAX: ffff8880691ae000 RBX: 00000000f7f54a39 RCX: ffffffff8100bb62
RDX: 0000000000000000 RSI: ffffffff8100bb70 RDI: 0000000000000006
RBP: ffffc90001fa7f48 R08: ffff8880691ae000 R09: ffffed100d235c01
R10: ffffed100d235c00 R11: ffff8880691ae007 R12: ffffc90001fa7f58
R13: 00000000f7f54a39 R14: 0000000000000000 R15: ffffc90001fa7fd8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0063) knlGS:000000000a40d900
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000008494bb8 CR3: 0000000069121000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139
RIP: 0023:0xf7f54a39
Code: 00 00 00 89 d3 5b 5e 5f 5d c3 b8 80 96 98 00 eb c4 8b 04 24 c3 8b 1c
24 c3 8b 34 24 c3 8b 3c 24 c3 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90
90 90 90 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 002b:000000000848fd7c EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: 0000000000000000 RBX: 000000000848fda8 RCX: 0000000000000000
RDX: 0000000000000004 RSI: 00000000001316fa RDI: 0000000000000000
RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace ac89df3b204fd52e ]---
RIP: 0010:do_fast_syscall_32+0x760/0xe16 arch/x86/entry/common.c:422
Code: 0f 85 5e 06 00 00 49 8b 9c 24 80 00 00 00 4c 89 ee 45 31 f6 48 89 df
e8 ee 72 74 00 4c 39 eb 0f 85 78 fe ff ff e8 c0 71 74 00 <07> 07 07 07 07
07 07 07 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0018:ffffc90001fa7f10 EFLAGS: 00010093
RAX: ffff8880691ae000 RBX: 00000000f7f54a39 RCX: ffffffff8100bb62
RDX: 0000000000000000 RSI: ffffffff8100bb70 RDI: 0000000000000006
RBP: ffffc90001fa7f48 R08: ffff8880691ae000 R09: ffffed100d235c01
R10: ffffed100d235c00 R11: ffff8880691ae007 R12: ffffc90001fa7f58
R13: 00000000f7f54a39 R14: 0000000000000000 R15: ffffc90001fa7fd8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0063) knlGS:000000000a40d900
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000008494bb8 CR3: 0000000069121000 CR4: 00000000001426e0
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: bed72351 Merge tag 'kbuild-fixes-v5.5-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e459c1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=874bac2ff63646fa
dashboard link: https://syzkaller.appspot.com/bug?extid=6dc4f484e2c2106c429b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: i386
CC: [b...@alien8.de h...@zytor.com linux-...@vger.kernel.org
lu...@kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.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+6dc4f4...@syzkaller.appspotmail.com
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9336 Comm: syz-executor.5 Not tainted 5.5.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:do_fast_syscall_32+0x760/0xe16 arch/x86/entry/common.c:422
Code: 0f 85 5e 06 00 00 49 8b 9c 24 80 00 00 00 4c 89 ee 45 31 f6 48 89 df
e8 ee 72 74 00 4c 39 eb 0f 85 78 fe ff ff e8 c0 71 74 00 <07> 07 07 07 07
07 07 07 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0018:ffffc90001fa7f10 EFLAGS: 00010093
RAX: ffff8880691ae000 RBX: 00000000f7f54a39 RCX: ffffffff8100bb62
RDX: 0000000000000000 RSI: ffffffff8100bb70 RDI: 0000000000000006
RBP: ffffc90001fa7f48 R08: ffff8880691ae000 R09: ffffed100d235c01
R10: ffffed100d235c00 R11: ffff8880691ae007 R12: ffffc90001fa7f58
R13: 00000000f7f54a39 R14: 0000000000000000 R15: ffffc90001fa7fd8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0063) knlGS:000000000a40d900
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000008494bb8 CR3: 0000000069121000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139
RIP: 0023:0xf7f54a39
Code: 00 00 00 89 d3 5b 5e 5f 5d c3 b8 80 96 98 00 eb c4 8b 04 24 c3 8b 1c
24 c3 8b 34 24 c3 8b 3c 24 c3 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90
90 90 90 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 002b:000000000848fd7c EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: 0000000000000000 RBX: 000000000848fda8 RCX: 0000000000000000
RDX: 0000000000000004 RSI: 00000000001316fa RDI: 0000000000000000
RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace ac89df3b204fd52e ]---
RIP: 0010:do_fast_syscall_32+0x760/0xe16 arch/x86/entry/common.c:422
Code: 0f 85 5e 06 00 00 49 8b 9c 24 80 00 00 00 4c 89 ee 45 31 f6 48 89 df
e8 ee 72 74 00 4c 39 eb 0f 85 78 fe ff ff e8 c0 71 74 00 <07> 07 07 07 07
07 07 07 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0018:ffffc90001fa7f10 EFLAGS: 00010093
RAX: ffff8880691ae000 RBX: 00000000f7f54a39 RCX: ffffffff8100bb62
RDX: 0000000000000000 RSI: ffffffff8100bb70 RDI: 0000000000000006
RBP: ffffc90001fa7f48 R08: ffff8880691ae000 R09: ffffed100d235c01
R10: ffffed100d235c00 R11: ffff8880691ae007 R12: ffffc90001fa7f58
R13: 00000000f7f54a39 R14: 0000000000000000 R15: ffffc90001fa7fd8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0063) knlGS:000000000a40d900
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000008494bb8 CR3: 0000000069121000 CR4: 00000000001426e0
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
Apr 12, 2020, 11:40:09 PM4/12/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