invalid opcode in do_syscall_64

7 views
Skip to first unread message

syzbot

unread,
Sep 28, 2020, 1:19:15 PM9/28/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=103e1b27900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=bbfc79b70a557b7743c5
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17ab48a7900000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bbfc79...@syzkaller.appspotmail.com

IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 6372 Comm: syz-executor.0 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88808635c340 task.stack: ffff888097bf8000
RIP: 0010:arch_local_irq_enable arch/x86/include/asm/paravirt.h:789 [inline]
RIP: 0010:do_syscall_64+0x73/0x640 arch/x86/entry/common.c:280
RSP: 0018:ffff888097bfff00 EFLAGS: 00010082
RAX: dffffc0000000000 RBX: 00000000000000e4 RCX: 0000000000000000
RDX: 1ffffffff0fa2d23 RSI: 0000000000000001 RDI: ffff88808635cbc4
RBP: ffff888097bfff58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff87d16918
R13: ffff888097bfffd0 R14: ffff88808635c340 R15: 0000000000000000
FS: 00000000023ca940(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557975547f08 CR3: 0000000090b47000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x460fba
RSP: 002b:00007ffe05df0108 EFLAGS: 00000246 ORIG_RAX: 00000000000000e4
RAX: ffffffffffffffda RBX: 00000000000091f6 RCX: 0000000000460fba
RDX: 0000000000000000 RSI: 00007ffe05df0110 RDI: 0000000000000001
RBP: 0000000000000007 R08: 0000000000000000 R09: 00000000023ca940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffe05df0170 R14: 00000000000091bb R15: 00007ffe05df0180
Code: 34 8c 46 00 4c 89 e2 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 52 04 00 00 48 83 3d 19 fb d0 06 00 0f 70 07 70 <07> 00 e8 06 29 5b 00 fb 66 0f 1f 44 00 00 48 b8 00 00 00 00 00
RIP: arch_local_irq_enable arch/x86/include/asm/paravirt.h:789 [inline] RSP: ffff888097bfff00
RIP: do_syscall_64+0x73/0x640 arch/x86/entry/common.c:280 RSP: ffff888097bfff00
---[ end trace da58b62279ee4a4f ]---


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages