[syzbot] [kvm?] WARNING in kvm_put_kvm (2)

[syzbot] [kvm?] WARNING in kvm_put_kvm (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    15e7d45e786a Add linux-next specific files for 20241016
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1397b240580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c36416f1c54640c0
dashboard link: https://syzkaller.appspot.com/bug?extid=4f8d3ac3727ffc0ecd8a
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cf2ad43c81cc/disk-15e7d45e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c85347a66a1c/vmlinux-15e7d45e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/648cf8e59c13/bzImage-15e7d45e.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5483 at kernel/rcu/srcutree.c:656 cleanup_srcu_struct+0x404/0x4d0 kernel/rcu/srcutree.c:656
Modules linked in:
CPU: 0 UID: 0 PID: 5483 Comm: syz.3.30 Not tainted 6.12.0-rc3-next-20241016-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:cleanup_srcu_struct+0x404/0x4d0 kernel/rcu/srcutree.c:656
Code: 74 84 00 48 c7 03 00 00 00 00 48 83 c4 48 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 0f 0b 90 eb e7 90 0f 0b 90 eb e1 90 <0f> 0b 90 eb db 90 0f 0b 90 eb 0a 90 0f 0b 90 eb 04 90 0f 0b 90 48
RSP: 0018:ffffc900041ffc50 EFLAGS: 00010202
RAX: 0000000000000001 RBX: ffff88807b56f980 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffe8ffffd70298
RBP: 0000000000000001 R08: ffffe8ffffd7029f R09: 1ffffd1ffffae053
R10: dffffc0000000000 R11: fffff91ffffae054 R12: dffffc0000000000
R13: ffffc900049ca8b8 R14: ffffc900049c1a70 R15: ffff88807b56f800
FS:  0000555574edd500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3fd02e CR3: 000000007f93e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 kvm_destroy_vm virt/kvm/kvm_main.c:1357 [inline]
 kvm_put_kvm+0xf25/0x1350 virt/kvm/kvm_main.c:1386
 kvm_vm_release+0x43/0x50 virt/kvm/kvm_main.c:1409
 __fput+0x23c/0xa50 fs/file_table.c:434
 task_work_run+0x24f/0x310 kernel/task_work.c:239
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0x168/0x370 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fba34b7dff9
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:00007ffc914498d8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fba34d37a80 RCX: 00007fba34b7dff9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fba34d37a80 R08: 0000000000000006 R09: 00007ffc91449bcf
R10: 00000000003ffd50 R11: 0000000000000246 R12: 0000000000011abb
R13: 00007ffc914499e0 R14: 0000000000000032 R15: ffffffffffffffff
 </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

Re: [syzbot] [kvm?] WARNING in kvm_put_kvm (2)

[Sean Christopherson]

On Wed, Oct 23, 2024, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    15e7d45e786a Add linux-next specific files for 20241016
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1397b240580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c36416f1c54640c0
> dashboard link: https://syzkaller.appspot.com/bug?extid=4f8d3ac3727ffc0ecd8a
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/cf2ad43c81cc/disk-15e7d45e.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/c85347a66a1c/vmlinux-15e7d45e.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/648cf8e59c13/bzImage-15e7d45e.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+4f8d3ac3727ffc0ecd8a@syzkaller.appspotmail.com

Yet another bcachefs shutdown problem.

#syz set subsystems: bcachefs

[   88.514126][ T5826] bcachefs (loop1): flushing journal and stopping allocators complete, journal seq 4
[   88.569826][ T5836] EXT4-fs (loop2): unmounting filesystem 00000000-0000-0000-0000-000000000000.
[   88.618725][ T5826] bcachefs (loop1): clean shutdown complete, journal seq 5
[   88.807819][ T5826] bcachefs (loop1): marking filesystem clean
[   89.094513][ T5826] bcachefs (loop1): shutdown complete
[   89.339441][ T6085] loop3: detected capacity change from 0 to 32768
[   89.629580][ T6096] loop4: detected capacity change from 0 to 40427
[   89.700754][ T6096] F2FS-fs (loop4): build fault injection attr: rate: 771, type: 0x1fffff
[   90.062540][ T6085] XFS (loop3): Mounting V5 Filesystem c496e05e-540d-4c72-b591-04d79d8b4eeb
[   90.081642][ T6096] F2FS-fs (loop4): invalid crc value
[   90.127830][ T6098] tty tty20: ldisc open failed (-12), clearing slot 19
[   90.438369][ T6096] F2FS-fs (loop4): Found nat_bits in checkpoint
[   90.558422][ T6085] XFS (loop3): Ending clean mount
[   90.619095][ T6115] loop0: detected capacity change from 0 to 128
[   90.643095][ T6085] XFS (loop3): Unmounting Filesystem c496e05e-540d-4c72-b591-04d79d8b4eeb
[   90.671995][ T6096] F2FS-fs (loop4): Mounted with checkpoint version = 48b305e5
[   91.300054][ T6117] syz.0.30 (6117): drop_caches: 2
[   91.503301][ T6118] syz.4.29: attempt to access beyond end of device
[   91.503301][ T6118] loop4: rw=2049, sector=77824, nr_sectors = 144 limit=40427
[   91.556455][ T6096] F2FS-fs (loop4): inject lock_op in f2fs_trylock_op of f2fs_write_single_data_page+0xd20/0x1bd0
[   91.604651][ T6096] syz.4.29: attempt to access beyond end of device
[   91.604651][ T6096] loop4: rw=2049, sector=77968, nr_sectors = 112 limit=40427
[   91.632912][ T6091] ------------[ cut here ]------------
[   91.638499][ T6091] WARNING: CPU: 0 PID: 6091 at kernel/rcu/srcutree.c:681 cleanup_srcu_struct+0x404/0x4d0