From: syzbot <syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com>
To: dwmw2@infradead.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, paulmck@kernel.org,
pbonzini@redhat.com, seanjc@kernel.org,
suryasaimadhu369@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kvm-x86?] [kvm?] WARNING: locking bug in kvm_xen_set_evtchn_fast
Date: Sun, 09 Aug 2026 04:34:02 -0700 [thread overview]
Message-ID: <6a7865aa.9c11d2ce.289b96.00ce.GAE@google.com> (raw)
In-Reply-To: <e8e1fbbe24ddad3850d77aed52a22a6e3f620cb3.camel@infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com
Tested-by: syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com
Tested on:
commit: 230abd62 KVM: pfncache: Use a dedicated SRCU domain in..
git tree: git://git.infradead.org/users/dwmw2/linux.git xen-rcu-fixed
console output: https://syzkaller.appspot.com/x/log.txt?x=110522c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9cef045500682f6b
dashboard link: https://syzkaller.appspot.com/bug?extid=919877893c9d28162dc2
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-09 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 12:19 [PATCH] KVM: x86/xen: Use read_trylock() for GPC locks in hardirq paths sai madhu
2026-08-07 12:19 ` sai madhu
2026-08-07 12:28 ` sashiko-bot
2026-08-09 9:42 ` David Woodhouse
2026-08-09 11:34 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-10 11:28 [syzbot] [kvm-x86?] [kvm?] WARNING: locking bug in kvm_xen_set_evtchn_fast David Woodhouse
2026-08-10 14:00 ` 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=6a7865aa.9c11d2ce.289b96.00ce.GAE@google.com \
--to=syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@kernel.org \
--cc=suryasaimadhu369@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox