From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+4f8d3ac3727ffc0ecd8a@syzkaller.appspotmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kvm?] WARNING in kvm_put_kvm (2)
Date: Thu, 16 Jan 2025 10:01:28 -0800 [thread overview]
Message-ID: <Z4lJeDIHfFT9_GG6@google.com> (raw)
In-Reply-To: <6719eaeb.050a0220.1e4b4d.00a0.GAE@google.com>
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
prev parent reply other threads:[~2025-01-16 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 6:36 [syzbot] [kvm?] WARNING in kvm_put_kvm (2) syzbot
2025-01-16 18:01 ` Sean Christopherson [this message]
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=Z4lJeDIHfFT9_GG6@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzbot+4f8d3ac3727ffc0ecd8a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.