public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3)
@ 2025-01-02  9:06 syzbot
  2025-02-26 17:36 ` syzbot
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: syzbot @ 2025-01-02  9:06 UTC (permalink / raw)
  To: kvm, linux-kernel, pbonzini, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    059dd502b263 Merge tag 'block-6.13-20241228' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c9b2c4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=aa8dc22aa6de51f5
dashboard link: https://syzkaller.appspot.com/bug?extid=cde12433b6c56f55d9ed
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-059dd502.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2125981e6709/vmlinux-059dd502.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ffdf1326e5e4/bzImage-059dd502.xz

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

------------[ cut here ]------------
WARNING: CPU: 3 PID: 6643 at arch/x86/kvm/../../../virt/kvm/pfncache.c:267 __kvm_gpc_refresh+0x174b/0x2390 virt/kvm/pfncache.c:267
Modules linked in:
CPU: 3 UID: 0 PID: 6643 Comm: syz.1.195 Not tainted 6.13.0-rc4-syzkaller-00078-g059dd502b263 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:__kvm_gpc_refresh+0x174b/0x2390 virt/kvm/pfncache.c:267
Code: c1 ea 03 80 3c 02 00 0f 85 dc 09 00 00 48 8b 3c 24 49 89 9f 08 01 00 00 31 db e8 30 20 14 0a e9 44 f4 ff ff e8 b6 e7 81 00 90 <0f> 0b 90 e9 31 f4 ff ff 4c 8b 7c 24 60 e8 a3 e7 81 00 31 db e9 e5
RSP: 0018:ffffc90004aa7230 EFLAGS: 00010283
RAX: 00000000000008c2 RBX: ffffffffffffffff RCX: ffffc90007221000
RDX: 0000000000080000 RSI: ffffffff81182dfa RDI: 0000000000000000
RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: ffffffff961eaed8 R12: ffff888000000000
R13: ffffc90005c4a401 R14: ffff887fffffff01 R15: ffffc90005c4a408
FS:  00007f0d642716c0(0000) GS:ffff88806a900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000053494000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 kvm_gpc_refresh+0xc3/0x140 virt/kvm/pfncache.c:382
 kvm_xen_set_evtchn.part.0+0x19c/0x270 arch/x86/kvm/xen.c:1878
 kvm_xen_set_evtchn arch/x86/kvm/xen.c:1968 [inline]
 kvm_xen_hvm_evtchn_send+0x231/0x290 arch/x86/kvm/xen.c:1958
 kvm_arch_vm_ioctl+0x119b/0x1d10 arch/x86/kvm/x86.c:7256
 kvm_vm_ioctl+0x1a87/0x3df0 virt/kvm/kvm_main.c:5241
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:906 [inline]
 __se_sys_ioctl fs/ioctl.c:892 [inline]
 __x64_sys_ioctl+0x190/0x200 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0d63385d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0d64271038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0d63575fa0 RCX: 00007f0d63385d29
RDX: 0000000020000180 RSI: 00000000400caed0 RDI: 0000000000000006
RBP: 00007f0d63401b08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f0d63575fa0 R15: 00007fff66828448
 </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.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3)
  2025-01-02  9:06 [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3) syzbot
@ 2025-02-26 17:36 ` syzbot
  2026-03-09  4:25 ` Forwarded: " syzbot
  2026-03-09  5:15 ` Forwarded: Re: [syzbot] [kvm?] " syzbot
  2 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2025-02-26 17:36 UTC (permalink / raw)
  To: kvm, linux-kernel, pbonzini, syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    e5d3fd687aac Add linux-next specific files for 20250218
git tree:       linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11e1003f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4e945b2fe8e5992f
dashboard link: https://syzkaller.appspot.com/bug?extid=cde12433b6c56f55d9ed
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=145af7a4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17e966e4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef079ccd2725/disk-e5d3fd68.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99f2123d6831/vmlinux-e5d3fd68.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eadfc9520358/bzImage-e5d3fd68.xz

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

kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5835 at arch/x86/kvm/../../../virt/kvm/pfncache.c:267 __kvm_gpc_refresh+0x11ff/0x1380 virt/kvm/pfncache.c:267
Modules linked in:
CPU: 1 UID: 0 PID: 5835 Comm: syz-executor401 Not tainted 6.14.0-rc3-next-20250218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__kvm_gpc_refresh+0x11ff/0x1380 virt/kvm/pfncache.c:267
Code: c6 05 69 55 f0 0e 01 48 c7 c7 89 2e 2b 8e be 24 04 00 00 48 c7 c2 a0 eb 21 8c e8 3c 36 66 00 e9 78 f1 ff ff e8 62 c0 8a 00 90 <0f> 0b 90 41 be ea ff ff ff e9 51 fe ff ff e8 4e c0 8a 00 90 0f 0b
RSP: 0018:ffffc9000406f140 EFLAGS: 00010293
RAX: ffffffff81373e7e RBX: ffffffffffffff01 RCX: ffff888035118000
RDX: 0000000000000000 RSI: ffff888000000000 RDI: ffff887fffffffff
RBP: ffffc9000406f2d0 R08: ffffffff81372d49 R09: 1ffffffff207b48e
R10: dffffc0000000000 R11: fffffbfff207b48f R12: ffff887fffffffff
R13: dffffc0000000000 R14: ffff888000000000 R15: ffffc900030f73f8
FS:  0000555565e72380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005654f4befc30 CR3: 000000007ecca000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 kvm_gpc_refresh+0xc6/0x110 virt/kvm/pfncache.c:382
 kvm_xen_set_evtchn+0x165/0x230 arch/x86/kvm/xen.c:1933
 kvm_xen_hvm_evtchn_send+0x1fa/0x370 arch/x86/kvm/xen.c:2013
 kvm_arch_vm_ioctl+0xe4d/0x17c0 arch/x86/kvm/x86.c:7262
 kvm_vm_ioctl+0x876/0xd70 virt/kvm/kvm_main.c:5285
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:906 [inline]
 __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2a11846429
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff5d46cb48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000400000000000 RCX: 00007f2a11846429
RDX: 0000400000000180 RSI: 00000000400caed0 RDI: 0000000000000001
RBP: 00007f2a118b9610 R08: 00007fff5d46cd18 R09: 00007fff5d46cd18
R10: 00007fff5d46cd18 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff5d46cd08 R14: 0000000000000001 R15: 0000000000000001
 </TASK>


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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Forwarded: WARNING in __kvm_gpc_refresh (3)
  2025-01-02  9:06 [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3) syzbot
  2025-02-26 17:36 ` syzbot
@ 2026-03-09  4:25 ` syzbot
  2026-03-09  5:15 ` Forwarded: Re: [syzbot] [kvm?] " syzbot
  2 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2026-03-09  4:25 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: WARNING in __kvm_gpc_refresh (3)
Author: phind.uet@gmail.com

#syz test:
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Forwarded: Re: [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3)
  2025-01-02  9:06 [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3) syzbot
  2025-02-26 17:36 ` syzbot
  2026-03-09  4:25 ` Forwarded: " syzbot
@ 2026-03-09  5:15 ` syzbot
  2 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2026-03-09  5:15 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3)
Author: phind.uet@gmail.com

On 9/3/26 12:39, syzbot wrote:
> Hello,
> 
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> WARNING in __kvm_gpc_refresh
> 
> ------------[ cut here ]------------
> kvm_is_error_gpa(gpa) == kvm_is_error_hva(uhva)
> WARNING: arch/x86/kvm/../../../virt/kvm/pfncache.c:267 at __kvm_gpc_refresh+0x1992/0x22c0 virt/kvm/pfncache.c:267, CPU#0: syz.0.17/6390
> Modules linked in:
> CPU: 0 UID: 0 PID: 6390 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> RIP: 0010:__kvm_gpc_refresh+0x1992/0x22c0 virt/kvm/pfncache.c:267
> Code: 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 26 08 00 00 48 8b 04 24 31 db 48 8b a8 10 01 00 00 e9 cf f0 ff ff e8 8f 47 86 00 90 <0f> 0b 90 e9 92 f7 ff ff e8 81 47 86 00 48 85 db 0f 84 e9 ed ff ff
> RSP: 0018:ffffc9000370f250 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffffffffffffffff RCX: ffffffff81836719
> RDX: ffff88803418a4c0 RSI: ffffffff81837fd1 RDI: ffff88803418a4c0
> RBP: ffffffffffffff01 R08: 0000000000000000 R09: 0000000000000001
> R10: 0000000000000001 R11: 0000000000000001 R12: ffff888000000000
> R13: ffff888000000001 R14: ffff888000000000 R15: ffffc9000370f468
> FS:  00007fb4a497e6c0(0000) GS:ffff8880d6331000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000055dccffea00c CR3: 0000000039576000 CR4: 0000000000352ef0
> Call Trace:
>   <TASK>
>   kvm_gpc_refresh+0xc9/0x190 virt/kvm/pfncache.c:382
>   kvm_xen_set_evtchn.part.0+0x168/0x230 arch/x86/kvm/xen.c:1942
>   kvm_xen_set_evtchn arch/x86/kvm/xen.c:2043 [inline]
>   kvm_xen_hvm_evtchn_send+0x22f/0x290 arch/x86/kvm/xen.c:2033
>   kvm_arch_vm_ioctl+0x13ac/0x18d0 arch/x86/kvm/x86.c:7537
>   kvm_vm_ioctl+0x1564/0x4080 virt/kvm/kvm_main.c:5390
>   vfs_ioctl fs/ioctl.c:51 [inline]
>   __do_sys_ioctl fs/ioctl.c:597 [inline]
>   __se_sys_ioctl fs/ioctl.c:583 [inline]
>   __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
>   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>   do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fb4a3b9aeb9
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fb4a497e028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 00007fb4a3e15fa0 RCX: 00007fb4a3b9aeb9
> RDX: 0000200000000980 RSI: 00000000400caed0 RDI: 0000000000000004
> RBP: 00007fb4a3c08c1f R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007fb4a3e16038 R14: 00007fb4a3e15fa0 R15: 00007ffe4fe93708
>   </TASK>
> 
> 
> Tested on:
> 
> commit:         a0ae2a25 Add linux-next specific files for 20260306
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12c3aa02580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=a2b2e6917734f438
> dashboard link: https://syzkaller.appspot.com/bug?extid=cde12433b6c56f55d9ed
> compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> 
> Note: no patches were applied.
#syz test:
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-03-09  5:15 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-02  9:06 [syzbot] [kvm?] WARNING in __kvm_gpc_refresh (3) syzbot
2025-02-26 17:36 ` syzbot
2026-03-09  4:25 ` Forwarded: " syzbot
2026-03-09  5:15 ` Forwarded: Re: [syzbot] [kvm?] " syzbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox