From: Oliver Upton <oupton@kernel.org>
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: maz@kernel.org, joey.gouly@arm.com, seiden@linux.ibm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, will@kernel.org, kees@kernel.org,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] KVM: arm64: vgic-its: Serialize translation cache invalidation under its_lock
Date: Tue, 2 Jun 2026 14:26:16 -0700 [thread overview]
Message-ID: <ah9KeH8bFl8NOveO@kernel.org> (raw)
In-Reply-To: <ah6Lsi4MfKUU6wBR@v4bel>
Hi Hyunwoo,
Thanks for respinning.
On Tue, Jun 02, 2026 at 04:52:18PM +0900, Hyunwoo Kim wrote:
> @@ -607,17 +609,16 @@ void vgic_its_invalidate_all_caches(struct kvm *kvm)
> struct kvm_device *dev;
> struct vgic_its *its;
>
> - rcu_read_lock();
> + guard(mutex)(&kvm->lock);
Urgh, entirely my mistake but we can get here holding the vcpu->mutex
which is an ordering bug. We can defer the locking cleanup as a long
term fix (which I still want) and take what you had before in v1.
Sorry for the noise.
Thanks,
Oliver
> - list_for_each_entry_rcu(dev, &kvm->devices, vm_node) {
> + list_for_each_entry(dev, &kvm->devices, vm_node) {
> if (dev->ops != &kvm_arm_vgic_its_ops)
> continue;
>
> its = dev->private;
> + guard(mutex)(&its->its_lock);
> vgic_its_invalidate_cache(its);
> }
> -
> - rcu_read_unlock();
> }
>
> int vgic_its_resolve_lpi(struct kvm *kvm, struct vgic_its *its,
> @@ -1725,8 +1726,10 @@ static void vgic_mmio_write_its_ctlr(struct kvm *kvm, struct vgic_its *its,
> goto out;
>
> its->enabled = !!(val & GITS_CTLR_ENABLE);
> - if (!its->enabled)
> + if (!its->enabled) {
> + guard(mutex)(&its->its_lock);
> vgic_its_invalidate_cache(its);
> + }
>
> /*
> * Try to process any pending commands. This function bails out early
> --
> 2.43.0
>
prev parent reply other threads:[~2026-06-02 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 7:52 [PATCH v2] KVM: arm64: vgic-its: Serialize translation cache invalidation under its_lock Hyunwoo Kim
2026-06-02 21:26 ` Oliver Upton [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=ah9KeH8bFl8NOveO@kernel.org \
--to=oupton@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=imv4bel@gmail.com \
--cc=joey.gouly@arm.com \
--cc=kees@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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