[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170665083753.694736.5736115942255110234.b4-ty@kernel.org>
Date: Tue, 30 Jan 2024 21:40:43 +0000
From: Marc Zyngier <maz@...nel.org>
To: Suzuki K Poulose <suzuki.poulose@....com>,
Oliver Upton <oliver.upton@...ux.dev>,
Sebastian Ene <sebastianene@...gle.com>,
Catalin Marinas <catalin.marinas@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Will Deacon <will@...nel.org>,
James Morse <james.morse@....com>
Cc: kvmarm@...ts.linux.dev,
kernel-team@...roid.com,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] KVM: arm64: Fix circular locking dependency
On Wed, 24 Jan 2024 09:10:28 +0000, Sebastian Ene wrote:
> The rule inside kvm enforces that the vcpu->mutex is taken *inside*
> kvm->lock. The rule is violated by the pkvm_create_hyp_vm() which acquires
> the kvm->lock while already holding the vcpu->mutex lock from
> kvm_vcpu_ioctl(). Avoid the circular locking dependency altogether by
> protecting the hyp vm handle with the config_lock, much like we already
> do for other forms of VM-scoped data.
Applied to fixes, thanks!
[1/1] KVM: arm64: Fix circular locking dependency
commit: 10c02aad111df02088d1a81792a709f6a7eca6cc
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists