From: syzbot <syzbot+d4faf7db59e11f6fd1ab@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: test patch for d4faf7db59e11f6fd1ab
Date: Sun, 23 Aug 2026 03:10:27 -0700 [thread overview]
Message-ID: <6a8ac713.dbb3a75c.13dd47.004a.GAE@google.com> (raw)
In-Reply-To: <6a78d191.b50370da.49fe0.0042.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test patch for d4faf7db59e11f6fd1ab
Author: shpark061104@gmail.com
#syz test: git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -1297,6 +1297,7 @@ static void kvm_destroy_vm(struct kvm *kvm)
kvm_free_memslots(kvm, &kvm->__memslots[i][0]);
kvm_free_memslots(kvm, &kvm->__memslots[i][1]);
}
+ srcu_barrier(&kvm->irq_srcu);
cleanup_srcu_struct(&kvm->irq_srcu);
srcu_barrier(&kvm->srcu);
cleanup_srcu_struct(&kvm->srcu);
next prev parent reply other threads:[~2026-08-23 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 19:14 [syzbot] [kvm?] WARNING in kvm_put_kvm (3) syzbot
2026-08-23 9:33 ` Forwarded: test for d4faf7db59e11f6fd1ab syzbot
2026-08-23 10:10 ` syzbot [this message]
2026-08-24 3:57 ` syzbot
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=6a8ac713.dbb3a75c.13dd47.004a.GAE@google.com \
--to=syzbot+d4faf7db59e11f6fd1ab@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox