linux-kernel - RE: [PATCH v2] tools: memory-model: Make plain accesses carry dependencies

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: <43c7ea9ebdd14497b85633950b014240@huawei.com>
Date:   Sun, 4 Dec 2022 00:15:27 +0000
From:   Jonas Oberhauser <jonas.oberhauser@...wei.com>
To:     "paulmck@...nel.org" <paulmck@...nel.org>,
        "stern@...land.harvard.edu" <stern@...land.harvard.edu>
CC:     Boqun Feng <boqun.feng@...il.com>,
        "parri.andrea@...il.com" <parri.andrea@...il.com>,
        "will@...nel.org" <will@...nel.org>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "npiggin@...il.com" <npiggin@...il.com>,
        "dhowells@...hat.com" <dhowells@...hat.com>,
        "j.alglave@....ac.uk" <j.alglave@....ac.uk>,
        "luc.maranget@...ia.fr" <luc.maranget@...ia.fr>,
        "akiyks@...il.com" <akiyks@...il.com>,
        "dlustig@...dia.com" <dlustig@...dia.com>,
        "joel@...lfernandes.org" <joel@...lfernandes.org>,
        "urezki@...il.com" <urezki@...il.com>,
        "quic_neeraju@...cinc.com" <quic_neeraju@...cinc.com>,
        "frederic@...nel.org" <frederic@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] tools: memory-model: Make plain accesses carry
 dependencies

-----Original Message-----
From: Paul E. McKenney [mailto:paulmck@...nel.org] 
Sent: Sunday, December 4, 2022 12:11 AM
To: stern@...land.harvard.edu
> On Sat, Dec 03, 2022 at 04:32:19PM -0500, stern@...land.harvard.edu wrote:
> > My advice: Omit them both.
> It would be good to reference something or another.  ;-)

I also prefer to not refer to that presentation. 
If there is a feeling that more context is needed, I would first prefer to enhance the commit message itself in some way. (Personally I don't feel that this is needed, and the imho the issue stands by itself even without reference to OOTA, which could be resolved fully independently e.g. by Viktor's suggestion to just axiomatically forbid OOTA --- the issue addressed by this patch would still exist).
If that's not satisfactory, I would also consent to publishing the e-mails from the thread starting where I relayed Viktor's observation of the relaxed accesses, but I don't recall it saying anything substantially beyond the current commit log + the documentation included in the patch.

best wishes, jonas