Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry
Date: Mon, 1 Jun 2026 22:54:22 -0700	[thread overview]
Message-ID: <ah5wDnNJ7AKGLDxh@kernel.org> (raw)
In-Reply-To: <ah4yiavdXTB10P0d@v4bel>

On Tue, Jun 02, 2026 at 10:31:53AM +0900, Hyunwoo Kim wrote:
> On Mon, Jun 01, 2026 at 12:08:55PM -0700, Oliver Upton wrote:
> > Hi Hyunwoo,
> > 
> > Nice find.
> > 
> > On Mon, Jun 01, 2026 at 11:53:26PM +0900, Hyunwoo Kim wrote:
> > > vgic_its_invalidate_cache() walks the per-ITS translation cache with
> > > xa_for_each() and drops the cache's reference on each entry with
> > > vgic_put_irq(). It puts the iterated pointer, though, rather than the
> > > value returned by xa_erase().
> > > 
> > > The function is called from contexts that do not exclude one another: the
> > > ITS command handlers hold its_lock, the GITS_CTLR write path holds
> > > cmd_lock, and the path that clears EnableLPIs in a redistributor's
> > > GICR_CTLR holds neither. Two or more of them can drain the same cache
> > > concurrently, and if each one observes the same entry, erases it and then
> > > puts it, the single reference the cache holds on that entry is dropped
> > > more than once. The entry can then be freed while an ITE still maps it.
> > > 
> > > xa_erase() is atomic and returns the previous entry, so put only the entry
> > > that this context actually removed. The cache reference is then dropped
> > > exactly once per entry even when the invalidations run concurrently, and
> > > the behavior is unchanged when only one context runs.
> > 
> > Next time:
> > 
> > Cc: stable@vger.kernel.org
> > 
> > > Fixes: 8201d1028caa ("KVM: arm64: vgic-its: Maintain a translation cache per ITS")
> > > Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
> > > ---
> > >  arch/arm64/kvm/vgic/vgic-its.c | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/arm64/kvm/vgic/vgic-its.c b/arch/arm64/kvm/vgic/vgic-its.c
> > > index 1d7e5d560af4..1e3706ac3b8e 100644
> > > --- a/arch/arm64/kvm/vgic/vgic-its.c
> > > +++ b/arch/arm64/kvm/vgic/vgic-its.c
> > > @@ -597,8 +597,10 @@ static void vgic_its_invalidate_cache(struct vgic_its *its)
> > >  	unsigned long idx;
> > >  
> > >  	xa_for_each(&its->translation_cache, idx, irq) {
> > > -		xa_erase(&its->translation_cache, idx);
> > > -		vgic_put_irq(kvm, irq);
> > > +		/* Only the context that erases the entry drops its cache ref. */
> > > +		irq = xa_erase(&its->translation_cache, idx);
> > > +		if (irq)
> > > +			vgic_put_irq(kvm, irq);
> > >  	}
> > >  }
> > 
> > This definitely works but TBH I'd rather just plug the subtle race and
> > do invalidations behind the its_lock since it already nests with the
> > cmd_lock.
> 
> Thank you for the review.
> 
> > 
> > Could you give this a spin?
> 
> After testing, I've confirmed that this patch approach works well too.
> 
> Shall I submit v2 based on this fix?

Yes, please do.

Thanks,
Oliver


      reply	other threads:[~2026-06-02  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 14:53 [PATCH] KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry Hyunwoo Kim
2026-06-01 19:08 ` Oliver Upton
2026-06-02  1:31   ` Hyunwoo Kim
2026-06-02  5:54     ` 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=ah5wDnNJ7AKGLDxh@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=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