linux-kernel - Re: [PATCH] documentation/rcu: fix typo

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: <4d9430d4-735e-4da9-891b-7cff41a5b3de@paulmck-laptop>
Date:   Thu, 8 Jun 2023 11:41:49 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Tycho Andersen <tycho@...ho.pizza>
Cc:     Jonathan Corbet <corbet@....net>, rcu@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Tycho Andersen <tandersen@...flix.com>
Subject: Re: [PATCH] documentation/rcu: fix typo

On Wed, Jun 07, 2023 at 08:15:21AM -0600, Tycho Andersen wrote:
> From: Tycho Andersen <tandersen@...flix.com>
> 
> Signed-off-by: Tycho Andersen <tandersen@...flix.com>

Good eyes, queued, thank you!

Build a fence out of all those lockdep-RCU slats?  ;-)

							Thanx, Paul

> ---
>  Documentation/RCU/lockdep-splat.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/RCU/lockdep-splat.rst b/Documentation/RCU/lockdep-splat.rst
> index 2a5c79db57dc..bcbc4b3c88d7 100644
> --- a/Documentation/RCU/lockdep-splat.rst
> +++ b/Documentation/RCU/lockdep-splat.rst
> @@ -10,7 +10,7 @@ misuses of the RCU API, most notably using one of the rcu_dereference()
>  family to access an RCU-protected pointer without the proper protection.
>  When such misuse is detected, an lockdep-RCU splat is emitted.
>  
> -The usual cause of a lockdep-RCU slat is someone accessing an
> +The usual cause of a lockdep-RCU splat is someone accessing an
>  RCU-protected data structure without either (1) being in the right kind of
>  RCU read-side critical section or (2) holding the right update-side lock.
>  This problem can therefore be serious: it might result in random memory
> 
> base-commit: a4d7d701121981e3c3fe69ade376fe9f26324161
> -- 
> 2.34.1
>