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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <3c5a53e2-b5a9-4197-97a3-247abb7f3061@gmail.com>
Date: Sat, 8 Jun 2024 08:38:12 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: 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, Marco Elver <elver@...gle.com>,
 Daniel Lustig <dlustig@...dia.com>, Joel Fernandes <joel@...lfernandes.org>,
 Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF
 mentorship session citation

On 2024/06/05 13:02, Paul E. McKenney wrote:
> On Wed, Jun 05, 2024 at 10:57:27AM +0900, Akira Yokosawa wrote:
>> On Tue,  4 Jun 2024 15:14:19 -0700, Paul E. McKenney 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>
>>> 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>
>>
>> Paul,
>>
>> While reviewing this, I noticed that
>> tools/memory-model/Documentation/README has no mention of
>> access-marking.txt.
>>
>> It has no mention of glossary.txt or locking.txt, either.
>>
>> I'm not sure where are the right places in README for them.
>> Can you update it in a follow-up change?
>>
>> Anyway, for this change,
>>
>> Reviewed-by: Akira Yokosawa <akiyks@...il.com>
> 
> Thank you, and good catch!  Does the patch below look appropriate?

Well, I must say this is not what I expected.
Please see below.

> 
> 							Thanx, Paul
> 
> ------------------------------------------------------------------------
> 
> commit 834b22ba762fb59024843a64554d38409aaa82ec
> Author: Paul E. McKenney <paulmck@...nel.org>
> Date:   Tue Jun 4 20:59:35 2024 -0700
> 
>     tools/memory-model: Add access-marking.txt to README
>     
>     Given that access-marking.txt exists, this commit makes it easier to find.
>     
>     Reported-by: Akira Yokosawa <akiyks@...il.com>
>     Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
> 
> diff --git a/tools/memory-model/Documentation/README b/tools/memory-model/Documentation/README
> index db90a26dbdf40..304162743a5b8 100644
> --- a/tools/memory-model/Documentation/README
> +++ b/tools/memory-model/Documentation/README
> @@ -47,6 +47,10 @@ DESCRIPTION OF FILES
>  README
>  	This file.
>  
> +access-marking.txt
> +	Guidelines for marking intentionally concurrent accesses to
> +	shared memory.
> +
>  cheatsheet.txt
>  	Quick-reference guide to the Linux-kernel memory model.
>

What I expected was an entry in the bullet list in the upper half
of README which mentions access-marking.txt along with the update of
alphabetical list of files.

Updating the latter wouldn't worth bothering you.

And you are missing another comment WRT glossary.txt and locking.txt. ;-)

Let me suggest an idea of their positions in the bullet list where the
ordering is important.  Looks reasonable to you ?

  o   simple.txt
  o   ordering.txt
  o   locking.txt               <--new
  o   litmus-test.txt
  o   recipes.txt
  o   control-dependencies.txt
  o   access-marking.txt        <--new
  o   cheatsheet.txt
  o   explanation.txt
  o   references.txt
  o   glossary.txt              <--new

Have I made my point clear enough?

        Thanks, Akira