linux-kernel - Re: [patch V2 02/10] genirq/msi: Use lock guards for MSI descriptor locking

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: <20250313152652.00001b7f@huawei.com>
Date: Thu, 13 Mar 2025 15:26:52 +0000
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: LKML <linux-kernel@...r.kernel.org>, Marc Zyngier <maz@...nel.org>, Peter
 Zijlstra <peterz@...radead.org>, Nishanth Menon <nm@...com>, "Dhruva Gole"
	<d-gole@...com>, Tero Kristo <kristo@...nel.org>, Santosh Shilimkar
	<ssantosh@...nel.org>, Logan Gunthorpe <logang@...tatee.com>, Dave Jiang
	<dave.jiang@...el.com>, Jon Mason <jdmason@...zu.us>, Allen Hubbe
	<allenbh@...il.com>, <ntb@...ts.linux.dev>, Bjorn Helgaas
	<bhelgaas@...gle.com>, <linux-pci@...r.kernel.org>, Michael Kelley
	<mhklinux@...look.com>, Wei Liu <wei.liu@...nel.org>, Haiyang Zhang
	<haiyangz@...rosoft.com>, <linux-hyperv@...r.kernel.org>, Wei Huang
	<wei.huang2@....com>, Manivannan Sadhasivam
	<manivannan.sadhasivam@...aro.org>, "James E.J. Bottomley"
	<James.Bottomley@...senPartnership.com>, "Martin K. Petersen"
	<martin.petersen@...cle.com>, <linux-scsi@...r.kernel.org>, Jonathan Cameron
	<Jonathan.Cameron@...ei.com>
Subject: Re: [patch V2 02/10] genirq/msi: Use lock guards for MSI descriptor
 locking

On Thu, 13 Mar 2025 14:03:39 +0100 (CET)
Thomas Gleixner <tglx@...utronix.de> wrote:

> Provide a lock guard for MSI descriptor locking and update the core code
> accordingly.
> 
> No functional change intended.
> 
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@...wei.com>