linux-kernel - Re: [PATCH] tools/memory-model/Documentation: Fix SRCU section in explanation.txt

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: <fd718b41-a812-43a3-973b-b07a1381f062@nvidia.com>
Date: Tue, 22 Apr 2025 18:56:17 -0400
From: Joel Fernandes <joelagnelf@...dia.com>
To: paulmck@...nel.org, "Uladzislau Rezki (Sony)" <urezki@...il.com>
Cc: Joel Fernandes <joel@...lfernandes.org>, RCU <rcu@...r.kernel.org>,
 LKML <linux-kernel@...r.kernel.org>,
 Frederic Weisbecker <frederic@...nel.org>,
 Neeraj upadhyay <Neeraj.Upadhyay@....com>,
 Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH] tools/memory-model/Documentation: Fix SRCU section in
 explanation.txt



On 4/22/2025 6:55 PM, Joel Fernandes wrote:
> 
> 
> On 4/22/2025 1:56 PM, Paul E. McKenney wrote:
>> On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
>>> The SRCU read-side critical sections describes the difference between
>>> srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
>>> in a way that a last pair must occur on the same CPU.
>>>
>>> This is not true, the srcu_read_unlock() can happen on any CPU, but it
>>> must be performed by the same task that invoked srcu_read_lock().
>>>
>>> Signed-off-by: Uladzislau Rezki (Sony) <urezki@...il.com>
>>
>> Good catch!
>>
>> Reviewed-by: Paul E. McKenney <paulmck@...nel.org>
> 
> Applied, thanks.
> 

Oops, though this is memory model and not RCU per-se. Paul do you want to take
it or should I? ;)

 - Joel