linux-kernel - Re: [PATCH v4 01/10] KVM: Use dedicated mutex to protect kvm_usage

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: <1f037b5604deb5f83f05e709b2edf3063372518f.camel@intel.com>
Date: Fri, 30 Aug 2024 12:45:53 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "zhaotianrui@...ngson.cn" <zhaotianrui@...ngson.cn>, "seanjc@...gle.com"
	<seanjc@...gle.com>, "oliver.upton@...ux.dev" <oliver.upton@...ux.dev>,
	"chenhuacai@...nel.org" <chenhuacai@...nel.org>, "maobibo@...ngson.cn"
	<maobibo@...ngson.cn>, "palmer@...belt.com" <palmer@...belt.com>,
	"maz@...nel.org" <maz@...nel.org>, "pbonzini@...hat.com"
	<pbonzini@...hat.com>, "anup@...infault.org" <anup@...infault.org>,
	"paul.walmsley@...ive.com" <paul.walmsley@...ive.com>,
	"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>
CC: "Gao, Chao" <chao.gao@...el.com>, "kvm-riscv@...ts.infradead.org"
	<kvm-riscv@...ts.infradead.org>, "linux-riscv@...ts.infradead.org"
	<linux-riscv@...ts.infradead.org>, "loongarch@...ts.linux.dev"
	<loongarch@...ts.linux.dev>, "kvmarm@...ts.linux.dev"
	<kvmarm@...ts.linux.dev>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "kvm@...r.kernel.org"
	<kvm@...r.kernel.org>, "linux-mips@...r.kernel.org"
	<linux-mips@...r.kernel.org>, "Chen, Farrah" <farrah.chen@...el.com>
Subject: Re: [PATCH v4 01/10] KVM: Use dedicated mutex to protect
 kvm_usage_count to avoid deadlock


> Reviewed-by: Kai Huang <kai.huang@...el.com>
> Acked-by: Kai Huang <kai.huang@...el.com>
> 

Hmm I must have done a lot for me to receive two credits (and for most patches
in this series) :-)

I think one Reviewed-by tag is good enough :-)