Hello,
syzbot found the following issue on:
HEAD commit: 0347b1658399 Merge 5.10.93 into android12-5.10-lts
git tree: android12-5.10-lts
console output:
https://syzkaller.appspot.com/x/log.txt?x=171b47e4700000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e0f3947457f8d2a4
dashboard link:
https://syzkaller.appspot.com/bug?extid=adc3cb32385586bec859
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
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+adc3cb...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at drivers/vhost/vhost.c:2335!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 20136 Comm: vhost-20135 Tainted: G W 5.10.93-syzkaller-01028-g0347b1658399 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:vhost_get_vq_desc+0x2083/0x2090 drivers/vhost/vhost.c:2335
Code: 80 e1 07 80 c1 03 38 c1 0f 8c af fd ff ff 48 8b 7d 10 e8 e0 e0 09 fe 48 8b 55 10 e9 9d fd ff ff e8 a2 40 fe 00 e8 9d eb cf fd <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc900068cf9a0 EFLAGS: 00010287
RAX: ffffffff839cffe3 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90007361000 RSI: 0000000000000076 RDI: 0000000000000077
RBP: ffffc900068cfc08 R08: ffffffff839cf477 R09: 0000000000000001
R10: fffff52000d19f76 R11: 0000000000000000 R12: ffffc900068cfd80
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f23c6ea9058 CR3: 000000010a812000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vhost_vsock_handle_tx_kick+0x291/0xca0 drivers/vhost/vsock.c:464
vhost_worker+0x27d/0x420 drivers/vhost/vhost.c:372
kthread+0x371/0x390 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Modules linked in:
---[ end trace f33c5da4ec1f407d ]---
RIP: 0010:vhost_get_vq_desc+0x2083/0x2090 drivers/vhost/vhost.c:2335
Code: 80 e1 07 80 c1 03 38 c1 0f 8c af fd ff ff 48 8b 7d 10 e8 e0 e0 09 fe 48 8b 55 10 e9 9d fd ff ff e8 a2 40 fe 00 e8 9d eb cf fd <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc900068cf9a0 EFLAGS: 00010287
RAX: ffffffff839cffe3 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90007361000 RSI: 0000000000000076 RDI: 0000000000000077
RBP: ffffc900068cfc08 R08: ffffffff839cf477 R09: 0000000000000001
R10: fffff52000d19f76 R11: 0000000000000000 R12: ffffc900068cfd80
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffefc4e6d68 CR3: 000000010a812000 CR4: 00000000003506b0
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.