From: syzbot <syzbot+545f1326f405db4e1c3e@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, mlevitsk@redhat.com, pbonzini@redhat.com,
seanjc@google.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: [syzbot] [kvm?] WARNING in kvm_recalculate_apic_map
Date: Mon, 08 Jul 2024 06:46:27 -0700 [thread overview]
Message-ID: <000000000000c2a6b9061cbca3c3@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f3a2439f20d9 Merge tag 'rproc-v6.3' of git://git.kernel.or..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12e2d518c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=81f5afa0c201c8de
dashboard link: https://syzkaller.appspot.com/bug?extid=545f1326f405db4e1c3e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b7be60c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11a380a8c80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0719d575f3ac/disk-f3a2439f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4176aabb67b5/vmlinux-f3a2439f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2b0e3c0ab205/bzImage-f3a2439f.xz
The issue was bisected to:
commit 76e527509d37a15ff1714ddd003384f5f25fd3fc
Author: Sean Christopherson <seanjc@google.com>
Date: Fri Jan 6 01:12:52 2023 +0000
KVM: x86: Skip redundant x2APIC logical mode optimized cluster setup
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=124fbe60c80000
final oops: https://syzkaller.appspot.com/x/report.txt?x=114fbe60c80000
console output: https://syzkaller.appspot.com/x/log.txt?x=164fbe60c80000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+545f1326f405db4e1c3e@syzkaller.appspotmail.com
Fixes: 76e527509d37 ("KVM: x86: Skip redundant x2APIC logical mode optimized cluster setup")
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5078 at arch/x86/kvm/lapic.c:330 kvm_recalculate_logical_map arch/x86/kvm/lapic.c:330 [inline]
WARNING: CPU: 0 PID: 5078 at arch/x86/kvm/lapic.c:330 kvm_recalculate_apic_map+0x1267/0x14e0 arch/x86/kvm/lapic.c:413
Modules linked in:
CPU: 0 PID: 5078 Comm: syz-executor294 Not tainted 6.2.0-syzkaller-12485-gf3a2439f20d9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
RIP: 0010:kvm_recalculate_logical_map arch/x86/kvm/lapic.c:330 [inline]
RIP: 0010:kvm_recalculate_apic_map+0x1267/0x14e0 arch/x86/kvm/lapic.c:413
Code: 8f ae a2 00 48 8b 3c 24 ba 01 00 00 00 be 04 00 00 00 e8 ac 83 fb ff 48 c7 44 24 08 00 00 00 00 e9 9b f7 ff ff e8 49 f9 6c 00 <0f> 0b e9 d2 f6 ff ff e8 3d f9 6c 00 4c 89 23 e9 c5 f6 ff ff 48 8b
RSP: 0018:ffffc900034af800 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff8880776f41c0 RSI: ffffffff811729b7 RDI: 0000000000000004
RBP: 0000000000000400 R08: 0000000000000004 R09: 0000000000000001
R10: 0000000000082000 R11: 0000000000000000 R12: ffff8880299f2000
R13: ffff88807d13c040 R14: dffffc0000000000 R15: 0000000000082000
FS: 0000555556467300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002004d008 CR3: 00000000760bd000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kvm_apic_set_state+0x468/0xeb0 arch/x86/kvm/lapic.c:2951
kvm_vcpu_ioctl_set_lapic arch/x86/kvm/x86.c:4858 [inline]
kvm_arch_vcpu_ioctl+0x2862/0x3f90 arch/x86/kvm/x86.c:5593
kvm_vcpu_ioctl+0x9ad/0xfe0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4255
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f5e46a52109
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcdc080378 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5e46a52109
RDX: 0000000020000880 RSI: 000000004400ae8f RDI: 0000000000000005
RBP: 00007f5e46a15b60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5e46a15bf0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
next reply other threads:[~2024-07-08 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 13:46 syzbot [this message]
2024-07-08 16:35 ` [syzbot] [kvm?] WARNING in kvm_recalculate_apic_map Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000c2a6b9061cbca3c3@google.com \
--to=syzbot+545f1326f405db4e1c3e@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox