linux-kernel - Re: [RFC PATCH 03/18] KVM: Drop kvm_count_lock and instead protect kvm_usage_count with kvm

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YwQ6wTmbja4h2TYZ@gao-cwp>
Date:   Tue, 23 Aug 2022 10:26:09 +0800
From:   Chao Gao <chao.gao@...el.com>
To:     <isaku.yamahata@...el.com>
CC:     <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <isaku.yamahata@...il.com>, Paolo Bonzini <pbonzini@...hat.com>,
        "Sean Christopherson" <seanjc@...gle.com>,
        Kai Huang <kai.huang@...el.com>,
        "Will Deacon" <will@...nel.org>
Subject: Re: [RFC PATCH 03/18] KVM: Drop kvm_count_lock and instead protect
 kvm_usage_count with kvm_lock

On Fri, Aug 19, 2022 at 11:00:09PM -0700, isaku.yamahata@...el.com wrote:
>From: Isaku Yamahata <isaku.yamahata@...el.com>
>
>Because kvm_count_lock unnecessarily complicates the KVM locking convention
>Drop kvm_count_lock and instead protect kvm_usage_count with kvm_lock for
>simplicity.
>
>Opportunistically add some comments on locking.
>
>Suggested-by: Sean Christopherson <seanjc@...gle.com>
>Signed-off-by: Isaku Yamahata <isaku.yamahata@...el.com>
>---
> static cpumask_var_t cpus_hardware_enabled;
>@@ -4999,6 +4998,8 @@ static void hardware_enable_nolock(void *junk)
> 	int cpu = raw_smp_processor_id();
> 	int r;
> 
>+	WARN_ON_ONCE(preemptible());
>+
> 	if (cpumask_test_cpu(cpu, cpus_hardware_enabled))
> 		return;
> 
>@@ -5015,10 +5016,10 @@ static void hardware_enable_nolock(void *junk)
> 
> static int kvm_starting_cpu(unsigned int cpu)
> {
>-	raw_spin_lock(&kvm_count_lock);
>+	mutex_lock(&kvm_lock);

kvm_starting_cpu() is called with interrupt disabled. So we cannot use
sleeping locks (e.g., mutex) here.