From: syzbot <syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com>
To: dwmw2@infradead.org, kvm@vger.kernel.org,
linux-kernel@vger.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: Mon, 10 Aug 2026 07:00:04 -0700 [thread overview]
Message-ID: <6a79d964.9c11d2ce.289b96.00ee.GAE@google.com> (raw)
In-Reply-To: <7e9fc104fec7d2776590edb95a94a7afbf109c57.camel@infradead.org>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo git://git.infradead.org/users/dwmw2/linux.git/xen-srcu-fixed: failed to run ["git" "-c" "core.hooksPath=/dev/null" "fetch" "--force" "73b08201ab8ba1d188f45210a65f33cb30e5efaf" "xen-srcu-fixed"]: exit status 128
Tested on:
commit: [unknown
git tree: git://git.infradead.org/users/dwmw2/linux.git xen-srcu-fixed
kernel config: https://syzkaller.appspot.com/x/.config?x=a94030c847137a18
dashboard link: https://syzkaller.appspot.com/bug?extid=919877893c9d28162dc2
compiler:
Note: no patches were applied.
next prev parent reply other threads:[~2026-08-10 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2026-08-11 7:51 ` David Woodhouse
2026-08-11 8:58 ` Aleksandr Nogikh
2026-08-11 12:12 ` David Woodhouse
2026-08-11 13:55 ` Aleksandr Nogikh
2026-08-11 15:01 ` syzbot
[not found] <CANp29Y4hp_VuJggdpabS2B_cNd0UCFrHKrgDg1wTuaZez=iSzA@mail.gmail.com>
2026-08-11 15:14 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-08-09 9:42 [PATCH] KVM: x86/xen: Use read_trylock() for GPC locks in hardirq paths David Woodhouse
2026-08-09 11:34 ` [syzbot] [kvm-x86?] [kvm?] WARNING: locking bug in kvm_xen_set_evtchn_fast 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=6a79d964.9c11d2ce.289b96.00ee.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=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 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.