invalid opcode in prepare_exit_to_usermode
12 views
Skip to first unread message
syzbot
May 22, 2020, 10:43:14 AM5/22/20
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: b9bbe6ed Linux 5.7-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c66202100000
kernel config: https://syzkaller.appspot.com/x/.config?x=9651fcb095b99b04
dashboard link: https://syzkaller.appspot.com/bug?extid=a3aedc2748752177c8b9
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
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+a3aedc...@syzkaller.appspotmail.com
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4189 Comm: systemd-udevd Not tainted 5.7.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:prepare_exit_to_usermode+0x11e/0x600 arch/x86/entry/common.c:190
Code: 03 42 8a 04 20 84 c0 0f 85 8c 04 00 00 8b 1b 31 ff 89 de e8 64 fb 72 00 85 db 74 0e e8 bb f7 72 00 eb 49 e8 b4 f7 72 00 eb 42 <48> 8d ff ff ff ff ff ff ff ff 48 c1 e8 03 42 8a 04 20 84 c0 0f 85
RSP: 0018:ffffc90000e77ef0 EFLAGS: 00010046
RAX: ffff8880a2dbc080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8880a2dbc080 R08: ffffffff81007f0c R09: ffffed10145b7811
R10: ffffed10145b7811 R11: 0000000000000000 R12: dffffc0000000000
R13: 1ffff110145b7810 R14: ffffc90000e77f58 R15: 0000000000000000
FS: 00007f25d1d058c0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000b90004 CR3: 00000000a2644000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
entry_SYSCALL_64_after_hwframe+0x49/0xb3
RIP: 0033:0x7f25d0b78335
Code: 69 db 2b 00 64 c7 00 16 00 00 00 b8 ff ff ff ff c3 0f 1f 40 00 83 ff 01 48 89 f0 77 30 48 89 c7 48 89 d6 b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 03 f3 c3 90 48 8b 15 31 db 2b 00 f7 d8 64 89
RSP: 002b:00007ffd6764f678 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: 0000000000000000 RBX: 0000560cccbb28d0 RCX: 00007f25d0b78335
RDX: 00007ffd6764f6b0 RSI: 00007ffd6764f6b0 RDI: 0000560cccbb18d0
RBP: 00007ffd6764f770 R08: 00007f25d0e371c8 R09: 0000000000001010
R10: 00007f25d0e36b58 R11: 0000000000000246 R12: 0000560cccbb18d0
R13: 0000560cccbb18e4 R14: 0000560cccba7ced R15: 0000560cccba7cf4
Modules linked in:
---[ end trace 51953aa772e9ab22 ]---
RIP: 0010:prepare_exit_to_usermode+0x11e/0x600 arch/x86/entry/common.c:190
Code: 03 42 8a 04 20 84 c0 0f 85 8c 04 00 00 8b 1b 31 ff 89 de e8 64 fb 72 00 85 db 74 0e e8 bb f7 72 00 eb 49 e8 b4 f7 72 00 eb 42 <48> 8d ff ff ff ff ff ff ff ff 48 c1 e8 03 42 8a 04 20 84 c0 0f 85
RSP: 0018:ffffc90000e77ef0 EFLAGS: 00010046
RAX: ffff8880a2dbc080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8880a2dbc080 R08: ffffffff81007f0c R09: ffffed10145b7811
R10: ffffed10145b7811 R11: 0000000000000000 R12: dffffc0000000000
R13: 1ffff110145b7810 R14: ffffc90000e77f58 R15: 0000000000000000
FS: 00007f25d1d058c0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000b90004 CR3: 00000000a2644000 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: b9bbe6ed Linux 5.7-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c66202100000
kernel config: https://syzkaller.appspot.com/x/.config?x=9651fcb095b99b04
dashboard link: https://syzkaller.appspot.com/bug?extid=a3aedc2748752177c8b9
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
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+a3aedc...@syzkaller.appspotmail.com
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4189 Comm: systemd-udevd Not tainted 5.7.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:prepare_exit_to_usermode+0x11e/0x600 arch/x86/entry/common.c:190
Code: 03 42 8a 04 20 84 c0 0f 85 8c 04 00 00 8b 1b 31 ff 89 de e8 64 fb 72 00 85 db 74 0e e8 bb f7 72 00 eb 49 e8 b4 f7 72 00 eb 42 <48> 8d ff ff ff ff ff ff ff ff 48 c1 e8 03 42 8a 04 20 84 c0 0f 85
RSP: 0018:ffffc90000e77ef0 EFLAGS: 00010046
RAX: ffff8880a2dbc080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8880a2dbc080 R08: ffffffff81007f0c R09: ffffed10145b7811
R10: ffffed10145b7811 R11: 0000000000000000 R12: dffffc0000000000
R13: 1ffff110145b7810 R14: ffffc90000e77f58 R15: 0000000000000000
FS: 00007f25d1d058c0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000b90004 CR3: 00000000a2644000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
entry_SYSCALL_64_after_hwframe+0x49/0xb3
RIP: 0033:0x7f25d0b78335
Code: 69 db 2b 00 64 c7 00 16 00 00 00 b8 ff ff ff ff c3 0f 1f 40 00 83 ff 01 48 89 f0 77 30 48 89 c7 48 89 d6 b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 03 f3 c3 90 48 8b 15 31 db 2b 00 f7 d8 64 89
RSP: 002b:00007ffd6764f678 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: 0000000000000000 RBX: 0000560cccbb28d0 RCX: 00007f25d0b78335
RDX: 00007ffd6764f6b0 RSI: 00007ffd6764f6b0 RDI: 0000560cccbb18d0
RBP: 00007ffd6764f770 R08: 00007f25d0e371c8 R09: 0000000000001010
R10: 00007f25d0e36b58 R11: 0000000000000246 R12: 0000560cccbb18d0
R13: 0000560cccbb18e4 R14: 0000560cccba7ced R15: 0000560cccba7cf4
Modules linked in:
---[ end trace 51953aa772e9ab22 ]---
RIP: 0010:prepare_exit_to_usermode+0x11e/0x600 arch/x86/entry/common.c:190
Code: 03 42 8a 04 20 84 c0 0f 85 8c 04 00 00 8b 1b 31 ff 89 de e8 64 fb 72 00 85 db 74 0e e8 bb f7 72 00 eb 49 e8 b4 f7 72 00 eb 42 <48> 8d ff ff ff ff ff ff ff ff 48 c1 e8 03 42 8a 04 20 84 c0 0f 85
RSP: 0018:ffffc90000e77ef0 EFLAGS: 00010046
RAX: ffff8880a2dbc080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8880a2dbc080 R08: ffffffff81007f0c R09: ffffed10145b7811
R10: ffffed10145b7811 R11: 0000000000000000 R12: dffffc0000000000
R13: 1ffff110145b7810 R14: ffffc90000e77f58 R15: 0000000000000000
FS: 00007f25d1d058c0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000b90004 CR3: 00000000a2644000 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
Aug 16, 2020, 10:42:10 AM8/16/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