linux-kernel - Re: [REVISED DOC on v3] Crossrelease Lockdep

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]

Message-ID: <20161108025425.GY2279@X58A-UD3R>
Date:   Tue, 8 Nov 2016 11:54:25 +0900
From:   Byungchul Park <byungchul.park@....com>
To:     peterz@...radead.org, mingo@...nel.org
Cc:     tglx@...utronix.de, walken@...gle.com, boqun.feng@...il.com,
        kirill@...temov.name, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, iamjoonsoo.kim@....com,
        akpm@...ux-foundation.org, npiggin@...il.com
Subject: Re: [REVISED DOC on v3] Crossrelease Lockdep

On Thu, Nov 03, 2016 at 05:18:13PM +0900, Byungchul Park wrote:
> Hello Peterz,
> 
> I tried to explain about what you asked me for.
> I wonder if I did it exactly. But I hope so.
> Please let me know if there's something more I need to add.

Just to be sure, are you concerning about sync and propagation delay of
memory contents including lock variables between cpus?

IMHO, it makes no difference. It's a true dependence once the dependency
is viewable by a cpu, which means anyway it actually happened. And please
remind all locks related to crosslocks are serialized via proper memory
barriers. I think this was already descibed in my document.

Is there something I missed? Please let me know.

Thank you,
Byungchul

> 
> Thank you,
> Byungchul