linux-kernel - Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 5 Jun 2024 09:52:38 +0200
From: Marco Elver <elver@...gle.com>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, 
	kernel-team@...a.com, mingo@...nel.org, stern@...land.harvard.edu, 
	parri.andrea@...il.com, will@...nel.org, peterz@...radead.org, 
	boqun.feng@...il.com, npiggin@...il.com, dhowells@...hat.com, 
	j.alglave@....ac.uk, luc.maranget@...ia.fr, akiyks@...il.com, 
	Daniel Lustig <dlustig@...dia.com>, Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF
 mentorship session citation

On Wed, 5 Jun 2024 at 00:14, Paul E. McKenney <paulmck@...nel.org> wrote:
>
> Add a citation to Marco's LF mentorship session presentation entitled
> "The Kernel Concurrency Sanitizer"
>
> [ paulmck: Apply Marco Elver feedback. ]
>
> Reported-by: Marco Elver <elver@...gle.com>
> Signed-off-by: Paul E. McKenney <paulmck@...nel.org>

Acked-by: Marco Elver <elver@...gle.com>

Thanks for adding.

> Cc: Alan Stern <stern@...land.harvard.edu>
> Cc: Andrea Parri <parri.andrea@...il.com>
> Cc: Will Deacon <will@...nel.org>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Boqun Feng <boqun.feng@...il.com>
> Cc: Nicholas Piggin <npiggin@...il.com>
> Cc: David Howells <dhowells@...hat.com>
> Cc: Jade Alglave <j.alglave@....ac.uk>
> Cc: Luc Maranget <luc.maranget@...ia.fr>
> Cc: Akira Yokosawa <akiyks@...il.com>
> Cc: Daniel Lustig <dlustig@...dia.com>
> Cc: Joel Fernandes <joel@...lfernandes.org>
> Cc: <linux-arch@...r.kernel.org>
> ---
>  tools/memory-model/Documentation/access-marking.txt | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/tools/memory-model/Documentation/access-marking.txt b/tools/memory-model/Documentation/access-marking.txt
> index 65778222183e3..f531b0837356b 100644
> --- a/tools/memory-model/Documentation/access-marking.txt
> +++ b/tools/memory-model/Documentation/access-marking.txt
> @@ -6,7 +6,8 @@ normal accesses to shared memory, that is "normal" as in accesses that do
>  not use read-modify-write atomic operations.  It also describes how to
>  document these accesses, both with comments and with special assertions
>  processed by the Kernel Concurrency Sanitizer (KCSAN).  This discussion
> -builds on an earlier LWN article [1].
> +builds on an earlier LWN article [1] and Linux Foundation mentorship
> +session [2].
>
>
>  ACCESS-MARKING OPTIONS
> @@ -31,7 +32,7 @@ example:
>         WRITE_ONCE(a, b + data_race(c + d) + READ_ONCE(e));
>
>  Neither plain C-language accesses nor data_race() (#1 and #2 above) place
> -any sort of constraint on the compiler's choice of optimizations [2].
> +any sort of constraint on the compiler's choice of optimizations [3].
>  In contrast, READ_ONCE() and WRITE_ONCE() (#3 and #4 above) restrict the
>  compiler's use of code-motion and common-subexpression optimizations.
>  Therefore, if a given access is involved in an intentional data race,
> @@ -594,5 +595,8 @@ REFERENCES
>  [1] "Concurrency bugs should fear the big bad data-race detector (part 2)"
>      https://lwn.net/Articles/816854/
>
> -[2] "Who's afraid of a big bad optimizing compiler?"
> +[2] "The Kernel Concurrency Sanitizer"
> +    https://www.linuxfoundation.org/webinars/the-kernel-concurrency-sanitizer
> +
> +[3] "Who's afraid of a big bad optimizing compiler?"
>      https://lwn.net/Articles/793253/
> --
> 2.40.1
>