* [PATCH] documentation/rcu: fix typo
@ 2023-06-07 14:15 Tycho Andersen
2023-06-08 18:41 ` Paul E. McKenney
0 siblings, 1 reply; 2+ messages in thread
From: Tycho Andersen @ 2023-06-07 14:15 UTC (permalink / raw)
To: Paul E . McKenney, Jonathan Corbet
Cc: rcu, linux-doc, linux-kernel, Tycho Andersen, Tycho Andersen
From: Tycho Andersen <tandersen@netflix.com>
Signed-off-by: Tycho Andersen <tandersen@netflix.com>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] documentation/rcu: fix typo
2023-06-07 14:15 [PATCH] documentation/rcu: fix typo Tycho Andersen
@ 2023-06-08 18:41 ` Paul E. McKenney
0 siblings, 0 replies; 2+ messages in thread
From: Paul E. McKenney @ 2023-06-08 18:41 UTC (permalink / raw)
To: Tycho Andersen
Cc: Jonathan Corbet, rcu, linux-doc, linux-kernel, Tycho Andersen
On Wed, Jun 07, 2023 at 08:15:21AM -0600, Tycho Andersen wrote:
> From: Tycho Andersen <tandersen@netflix.com>
>
> Signed-off-by: Tycho Andersen <tandersen@netflix.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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-06-08 18:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-07 14:15 [PATCH] documentation/rcu: fix typo Tycho Andersen
2023-06-08 18:41 ` Paul E. McKenney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).