[moderation] [kvm?] general protection fault in get_work_pool (2)

1 view
Skip to first unread message

syzbot

unread,
May 27, 2024, 2:03:29 AMMay 27
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5f16eb0549ab Merge tag 'char-misc-6.10-rc1' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157b643c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7f4625418c9ed5c8
dashboard link: https://syzkaller.appspot.com/bug?extid=fefd00a9bf09f36f5bc6
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [k...@vger.kernel.org linux-...@vger.kernel.org pbon...@redhat.com]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-5f16eb05.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20ac83ea5f8c/vmlinux-5f16eb05.xz
kernel image: https://storage.googleapis.com/syzbot-assets/31519c4f23c8/bzImage-5f16eb05.xz

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

Oops: general protection fault, probably for non-canonical address 0xe003fbfffff80000: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0x001fffffffc00000-0x001fffffffc00007]
CPU: 3 PID: 12342 Comm: syz-executor.3 Not tainted 6.9.0-syzkaller-11919-g5f16eb0549ab #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:get_work_pool+0xcb/0x1c0 kernel/workqueue.c:887
Code: 11 36 00 48 89 d8 5b 5d c3 cc cc cc cc e8 cd 11 36 00 48 81 e3 00 fe ff ff 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 da 00 00 00 48 8b 1b e8 a3 11 36 00 48 89 d8 5b
RSP: 0018:ffffc900202d7bf0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 001fffffffc00000 RCX: ffffffff81587362
RDX: 0003fffffff80000 RSI: ffffffff815873b3 RDI: 0000000000000007
RBP: 0000000000000004 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000000 R12: ffffc9000285f8a8
R13: 0000000000000001 R14: ffffe8ffad153bb8 R15: fffff5200050bf16
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:0000000057f93400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f7387270 CR3: 0000000026d20000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
start_flush_work kernel/workqueue.c:4123 [inline]
__flush_work+0x12f/0xc60 kernel/workqueue.c:4181
cleanup_srcu_struct+0x130/0x520 kernel/rcu/srcutree.c:660
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1351 [inline]
kvm_put_kvm+0x8df/0xb80 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1380
kvm_vm_release+0x42/0x60 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1403
__fput+0x408/0xbb0 fs/file_table.c:422
__fput_sync+0x47/0x50 fs/file_table.c:507
__do_sys_close fs/open.c:1555 [inline]
__se_sys_close fs/open.c:1540 [inline]
__ia32_sys_close+0x86/0x100 fs/open.c:1540
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x75/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf7263579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000ffb62b30 EFLAGS: 00000293 ORIG_RAX: 0000000000000006
RAX: ffffffffffffffda RBX: 000000000000000a RCX: 0000000057f93400
RDX: 0000000000000000 RSI: 00000000f73b9ff4 RDI: 00000000ffffffff
RBP: 00000000ffffffff R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:get_work_pool+0xcb/0x1c0 kernel/workqueue.c:887
Code: 11 36 00 48 89 d8 5b 5d c3 cc cc cc cc e8 cd 11 36 00 48 81 e3 00 fe ff ff 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 da 00 00 00 48 8b 1b e8 a3 11 36 00 48 89 d8 5b
RSP: 0018:ffffc900202d7bf0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 001fffffffc00000 RCX: ffffffff81587362
RDX: 0003fffffff80000 RSI: ffffffff815873b3 RDI: 0000000000000007
RBP: 0000000000000004 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000000 R12: ffffc9000285f8a8
R13: 0000000000000001 R14: ffffe8ffad153bb8 R15: fffff5200050bf16
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:0000000057f93400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f7387270 CR3: 0000000026d20000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 11 36 adc %esi,(%rsi)
2: 00 48 89 add %cl,-0x77(%rax)
5: d8 5b 5d fcomps 0x5d(%rbx)
8: c3 ret
9: cc int3
a: cc int3
b: cc int3
c: cc int3
d: e8 cd 11 36 00 call 0x3611df
12: 48 81 e3 00 fe ff ff and $0xfffffffffffffe00,%rbx
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 da mov %rbx,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 da 00 00 00 jne 0x10e
34: 48 8b 1b mov (%rbx),%rbx
37: e8 a3 11 36 00 call 0x3611df
3c: 48 89 d8 mov %rbx,%rax
3f: 5b pop %rbx


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages