linux-kernel - Re: [PATCH v2 1/1] RDMA/hfi1: Use RMW accessors for changing LNKCTL2

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]

Date: Sun, 05 May 2024 16:11:56 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Dennis Dalessandro <dennis.dalessandro@...nelisnetworks.com>, 
 Jason Gunthorpe <jgg@...pe.ca>, linux-rdma@...r.kernel.org, 
 linux-kernel@...r.kernel.org, 
 Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Lukas Wunner <lukas@...ner.de>, 
 Dean Luick <dean.luick@...nelisnetworks.com>
Subject: Re: [PATCH v2 1/1] RDMA/hfi1: Use RMW accessors for changing
 LNKCTL2


On Fri, 03 May 2024 16:36:40 +0300, Ilpo Järvinen wrote:
> Convert open coded RMW accesses for LNKCTL2 to use
> pcie_capability_clear_and_set_word() which makes its easier to
> understand what the code tries to do.
> 
> In addition, this futureproofs the code. LNKCTL2 is not really owned by
> any driver because it is a collection of control bits that PCI core
> might need to touch. RMW accessors already have support for proper
> locking for a selected set of registers to avoid losing concurrent
> updates (LNKCTL2 is not yet among the registers that need protection
> but likely will be in the future).
> 
> [...]

Applied, thanks!

[1/1] RDMA/hfi1: Use RMW accessors for changing LNKCTL2
      https://git.kernel.org/rdma/rdma/c/8f3b7103b41314

Best regards,
-- 
Leon Romanovsky <leon@...nel.org>