linux-kernel - Re: [PATCH v5 0/6] KVM: lockdep improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174957290974.2454024.11071746229021073521.git-patchwork-notify@kernel.org>
Date: Tue, 10 Jun 2025 16:28:29 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Maxim Levitsky <mlevitsk@...hat.com>
Cc: linux-riscv@...ts.infradead.org, kvm@...r.kernel.org,
 suzuki.poulose@....com, jingzhangos@...gle.com, hpa@...or.com,
 sebott@...hat.com, lishusen2@...wei.com, longman@...hat.com,
 tglx@...utronix.de, linux-arm-kernel@...ts.infradead.org,
 bhelgaas@...gle.com, bp@...en8.de, anup@...infault.org, will@...nel.org,
 palmer@...belt.com, glider@...gle.com, kvmarm@...ts.linux.dev,
 keisuke.nishimura@...ia.fr, yuzenghui@...wei.com, peterz@...radead.org,
 atishp@...shpatra.org, joey.gouly@....com, x86@...nel.org, maz@...nel.org,
 seanjc@...gle.com, andre.przywara@....com, jiangkunkun@...wei.com,
 rdunlap@...radead.org, pbonzini@...hat.com, boqun.feng@...il.com,
 catalin.marinas@....com, alex@...ti.fr, linux-kernel@...r.kernel.org,
 dave.hansen@...ux.intel.com, oliver.upton@...ux.dev,
 kvm-riscv@...ts.infradead.org, mingo@...hat.com, paul.walmsley@...ive.com,
 aou@...s.berkeley.edu
Subject: Re: [PATCH v5 0/6] KVM: lockdep improvements

Hello:

This series was applied to riscv/linux.git (fixes)
by Paolo Bonzini <pbonzini@...hat.com>:

On Mon, 12 May 2025 14:04:01 -0400 you wrote:
> This is	a continuation of my 'extract lock_all_vcpus/unlock_all_vcpus'
> patch series.
> 
> Implement the suggestion of using lockdep's "nest_lock" feature
> when locking all KVM vCPUs by adding mutex_trylock_nest_lock() and
> mutex_lock_killable_nest_lock() and use these functions	in the
> implementation of the
> kvm_trylock_all_vcpus()/kvm_lock_all_vcpus()/kvm_unlock_all_vcpus().
> 
> [...]

Here is the summary with links:
  - [v5,1/6] locking/mutex: implement mutex_trylock_nested
    https://git.kernel.org/riscv/c/c5b6ababd21a
  - [v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock
    https://git.kernel.org/riscv/c/fb49f07ba1d9
  - [v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus
    https://git.kernel.org/riscv/c/e4a454ced74c
  - [v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation
    https://git.kernel.org/riscv/c/c560bc9286e6
  - [v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs
    https://git.kernel.org/riscv/c/b586c5d21954
  - [v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs
    https://git.kernel.org/riscv/c/8f56770d114b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html