linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	Alexander Potapenko <glider@google.com>,
	Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/3] KVM: arm64: Assorted vgic fixes for 6.14
Date: Fri, 07 Feb 2025 18:10:49 +0000	[thread overview]
Message-ID: <86ed09tyl2.wl-maz@kernel.org> (raw)
In-Reply-To: <Z6ZLC1v5KU-zzbQR@linux.dev>

On Fri, 07 Feb 2025 18:03:55 +0000,
Oliver Upton <oliver.upton@linux.dev> wrote:
> 
> On Thu, Feb 06, 2025 at 03:20:57PM +0000, Marc Zyngier wrote:
> > Alexander, while fuzzing KVM/arm64, found an annoying set of problems,
> > all stemming from the fact that the vgic can be destroyed in parallel
> > with the rest of the guest still being live.
> > 
> > Yes, this is annoying.
> > 
> > Fixing this is not going to happen overnight (though I have some
> > ideas), but we can make what we have today a bit more robust.
> > 
> > This is what patch #2 is doing. Patch #1 is just removing a loud
> > WARN_ON() that serves little purpose, and patch #3 fixes the actual
> > bug that Alex reported.
> > 
> > Hopefully, none of that is controversial...
> 
> I'm a bit grumbly about slapping bandaids on the problem, but given the
> fact that glider reported all of this a while ago and we still haven't
> fixed it is enough to justify these patches. So:

Yeah, same here. I'm starting to think that we need to either prevent
the vgic from being asynchronously destroyed, or start refcounting all
IRQs just like LPIs. Which is very annoying since we don't have a
global namespace for SGIs and PPIs.

But maybe simply refcounting the vgic itself would be enough.
Thoughts?

> Reviewed-by: Oliver Upton <oliver.upton@linux.dev>

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2025-02-07 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 15:20 [PATCH 0/3] KVM: arm64: Assorted vgic fixes for 6.14 Marc Zyngier
2025-02-06 15:20 ` [PATCH 1/3] KVM: arm64: timer: Drop warning on failed interrupt signalling Marc Zyngier
2025-02-06 15:50   ` Alexander Potapenko
2025-02-06 15:20 ` [PATCH 2/3] KVM: arm64: vgic: Check for unallocated PPI/SPI arrays Marc Zyngier
2025-02-06 15:50   ` Alexander Potapenko
2025-02-06 15:21 ` [PATCH 3/3] KVM: arm64: vgic: Gracefully handle resetting an unallocated interrupt Marc Zyngier
2025-02-06 15:50   ` Alexander Potapenko
2025-02-07 18:03 ` [PATCH 0/3] KVM: arm64: Assorted vgic fixes for 6.14 Oliver Upton
2025-02-07 18:10   ` Marc Zyngier [this message]
2025-02-07 18:50     ` Oliver Upton
2025-02-08 15:15       ` Marc Zyngier

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=86ed09tyl2.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=glider@google.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).