linux-kernel - Re: [PATCH] PCI: Using lockless config space accessors based on Kconfig option

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: <87jz6sn5tw.ffs@tglx>
Date: Wed, 07 May 2025 11:11:23 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Lukas Wunner <lukas@...ner.de>, Zijiang Huang <huangzjsmile@...il.com>
Cc: bhelgaas@...gle.com, linux-pci@...r.kernel.org,
 linux-kernel@...r.kernel.org, Zijiang Huang <kerayhuang@...cent.com>, Hao
 Peng <flyingpeng@...cent.com>
Subject: Re: [PATCH] PCI: Using lockless config space accessors based on
 Kconfig option

On Wed, May 07 2025 at 09:53, Lukas Wunner wrote:
> On Wed, May 07, 2025 at 03:30:28PM +0800, Zijiang Huang wrote:
> The question is, why did the commit only replace raw_spin_lock()
> with pci_lock_config() in the in-kernel PCI accessors, but not in
> the user space accessors?  Is it safe to replace it there as well?

See comment above pci_cfg_access_lock() ...