linux-kernel - Re: [PATCH][v2] KVM: Remove obsolete comment about locking for kvm_io_bus

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: <174674537050.1513194.17959981986179733390.b4-ty@google.com>
Date: Thu,  8 May 2025 16:04:09 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, pbonzini@...hat.com, kvm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, lirongqing <lirongqing@...du.com>
Subject: Re: [PATCH][v2] KVM: Remove obsolete comment about locking for kvm_io_bus_read/write

On Tue, 06 May 2025 09:22:51 +0800, lirongqing wrote:
> Nobody is actually calling these functions with slots_lock held, The
> srcu_dereference() in kvm_io_bus_read/write() precisely communicates
> both what is being protected, and what provides the protection. so the
> comments are no longer needed

Applied to kvm-x86 misc, thanks!

[1/1] KVM: Remove obsolete comment about locking for kvm_io_bus_read/write
      https://github.com/kvm-x86/linux/commit/37d8bad41d2b

--
https://github.com/kvm-x86/linux/tree/next