[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175735577932.2363175.14048203051041035424.b4-ty@linux.dev>
Date: Mon, 8 Sep 2025 11:23:23 -0700
From: Oliver Upton <oliver.upton@...ux.dev>
To: jintack@...columbia.edu,
christoffer.dall@....com,
maz@...nel.org,
joey.gouly@....com,
suzuki.poulose@....com,
yuzenghui@...wei.com,
catalin.marinas@....com,
will@...nel.org,
linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
Julien Thierry <julien.thierry.kdev@...il.com>,
Alok Tiwari <alok.a.tiwari@...cle.com>
Cc: Oliver Upton <oliver.upton@...ux.dev>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] KVM: arm64: vgic: fix incorrect spinlock API usage
On Mon, 08 Sep 2025 11:04:11 -0700, Alok Tiwari wrote:
> The function vgic_flush_lr_state() is calling _raw_spin_unlock()
> instead of the proper raw_spin_unlock().
>
> _raw_spin_unlock() is an internal low-level API and should not
> be used directly; using raw_spin_unlock() ensures proper locking
> semantics in the vgic code.
>
> [...]
Applied to fixes, thanks!
[1/1] KVM: arm64: vgic: fix incorrect spinlock API usage
https://git.kernel.org/kvmarm/kvmarm/c/2d0478279fc7
--
Best,
Oliver
Powered by blists - more mailing lists