linux-kernel - Re: [PATCH tip/core/rcu 1/4] doc: Present the role of READ

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: <20201109122133.GL2594@hirez.programming.kicks-ass.net>
Date:   Mon, 9 Nov 2020 13:21:33 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     paulmck@...nel.org
Cc:     rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel-team@...com, mingo@...nel.org, jiangshanlai@...il.com,
        akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
        josh@...htriplett.org, tglx@...utronix.de, rostedt@...dmis.org,
        dhowells@...hat.com, edumazet@...gle.com, fweisbec@...il.com,
        oleg@...hat.com, joel@...lfernandes.org
Subject: Re: [PATCH tip/core/rcu 1/4] doc: Present the role of READ_ONCE()

On Thu, Nov 05, 2020 at 03:05:07PM -0800, paulmck@...nel.org wrote:
> From: "Paul E. McKenney" <paulmck@...nel.org>
> 
> This commit adds an explanation of the special cases where READ_ONCE()
> may be used in place of a member of the rcu_dereference() family.

I am confused, there is no actual difference between rcu_dereference()
and READ_ONCE() today. So we _may_ use READ_ONCE() at all times.

Now granted, we probably don't want that, but that does leave me
somewhat confused vs the wording here.