From: "shaikh.kamal" <shaikhkamal2012@gmail.com>
To: kvm@vger.kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com, dwmw@amazon.co.uk,
linux-kernel@vger.kernel.org,
syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com,
skhan@linuxfoundation.org, me@brighamcampbell.com,
"shaikh.kamal" <shaikhkamal2012@gmail.com>
Subject: [PATCH v2 0/1] KVM: x86/xen: Fix PREEMPT_RT sleeping lock bug
Date: Thu, 2 Apr 2026 07:00:22 +0530 [thread overview]
Message-ID: <20260402013022.21879-1-shaikhkamal2012@gmail.com> (raw)
In-Reply-To: <ac08V4TaM2yh9SY1@google.com>
Hi Sean,
Thanks for the detailed feedback. I've implemented v2 using unconditional
read_trylock() as you suggested.
Changes in v2:
- Use read_trylock() unconditionally (no in_hardirq() check)
- Apply trylock to both gpc lock acquisitions
- Return -EWOULDBLOCK on contention to use existing slow path
Changes from v1:
- v1 used irq_work deferral (rejected for code duplication)
- v2 uses trylock, leveraging existing slow path (cleaner)
Testing:
- PREEMPT_RT kernel: No crash with syzbot reproducer after 30+ min
- non-RT kernel: No regression
This minimal fix preserves compatibility with your planned gpc API cleanup.
Thanks,
Kamal
shaikh.kamal (1):
KVM: x86/xen: Use trylock for fast path event channel delivery
arch/x86/kvm/xen.c | 33 +++++++++++++++++++++++++++++----
1 file changed, 29 insertions(+), 4 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-04-02 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 13:15 [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT shaikh.kamal
2026-03-30 14:18 ` Steven Rostedt
2026-03-30 14:51 ` Woodhouse, David
2026-04-01 15:40 ` Sean Christopherson
2026-04-02 1:30 ` shaikh.kamal [this message]
2026-04-02 1:31 ` [PATCH v2 1/1] KVM: x86/xen: Use trylock for fast path event channel delivery shaikh.kamal
2026-04-02 6:36 ` Sebastian Andrzej Siewior
2026-04-02 22:40 ` Sean Christopherson
2026-04-02 6:42 ` [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT Sebastian Andrzej Siewior
2026-04-02 22:23 ` Sean Christopherson
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=20260402013022.21879-1-shaikhkamal2012@gmail.com \
--to=shaikhkamal2012@gmail.com \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@brighamcampbell.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+919877893c9d28162dc2@syzkaller.appspotmail.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