linux-kernel - LKMM: Making RMW barriers explicit

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-next>] [day] [month] [year] [list]

Message-ID: <72c804c8-2511-4349-a823-bc1de8bb729e@rowland.harvard.edu>
Date: Wed, 15 May 2024 21:43:17 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Hernan Ponce de Leon <hernan.poncedeleon@...weicloud.com>,
  Jonas Oberhauser <jonas.oberhauser@...weicloud.com>
Cc: "Paul E. McKenney" <paulmck@...nel.org>, linux-kernel@...r.kernel.org,
  linux-arch@...r.kernel.org, kernel-team@...a.com, parri.andrea@...il.com,
  boqun.feng@...il.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
  Joel Fernandes <joel@...lfernandes.org>
Subject: LKMM: Making RMW barriers explicit

Hernan and Jonas:

Can you explain more fully the changes you want to make to herd7 and/or 
the LKMM?  The goal is to make the memory barriers currently implicit in 
RMW operations explicit, but I couldn't understand how you propose to do 
this.

Are you going to change herd7 somehow, and if so, how?  It seems like 
you should want to provide sufficient information so that the .bell 
and .cat files can implement the appropriate memory barriers associated 
with each RMW operation.  What additional information is needed?  And 
how (explained in English, not by quoting source code) will the .bell 
and .cat files make use of this information?

Alan