public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: SeongJae Park <sj38.park@gmail.com>, perfbook@vger.kernel.org
Subject: [PATCH 09/13] defer/rcuusage: Add missing '()' for 'rcu_dereference()'
Date: Thu, 24 Nov 2022 10:57:59 -0800	[thread overview]
Message-ID: <20221124185803.8150-11-sj@kernel.org> (raw)
In-Reply-To: <20221124185803.8150-1-sj@kernel.org>

From: SeongJae Park <sj38.park@gmail.com>

A sentence is missing '()' for 'rcu_dereference()'.  Add it.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 defer/rcuusage.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defer/rcuusage.tex b/defer/rcuusage.tex
index ba13bd96..1dc4c2ca 100644
--- a/defer/rcuusage.tex
+++ b/defer/rcuusage.tex
@@ -645,7 +645,7 @@ It is important to note that \co{SLAB_TYPESAFE_BY_RCU} will
 prevent \co{kmem_cache_alloc()} from immediately reallocating
 memory that was just now freed via \co{kmem_cache_free()}!
 In fact, the \co{SLAB_TYPESAFE_BY_RCU}-protected data structure
-just returned by \co{rcu_dereference} might be freed and reallocated
+just returned by \co{rcu_dereference()} might be freed and reallocated
 an arbitrarily large number of times, even when under the protection
 of \co{rcu_read_lock()}.
 Instead, \co{SLAB_TYPESAFE_BY_RCU} operates by preventing
-- 
2.17.1


  parent reply	other threads:[~2022-11-24 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 18:57 [PATCH 00/13] Minor fixes for defer/ SeongJae Park
2022-11-24 18:57 ` [PATCH 01/13] defer/rcuintro: Clearly point the QSBR described section SeongJae Park
2022-11-24 18:57 ` [PATCH 02/13] defer/rcufundamental: Add non-breaking spaces SeongJae Park
2022-11-24 18:57 ` [PATCH 03/13] defer/rcuapi: Add missed unbreakable spaces SeongJae Park
2022-11-24 18:57 ` [PATCH 04/13] defer/rcuapi: Use \co{} for boolean return value SeongJae Park
2022-11-24 18:57 ` [PATCH 05/13] defer/seqlock: " SeongJae Park
2022-11-24 18:57 ` [PATCH 06/13] defer/rcuusage: Call paragraphs paragraphs, not sections SeongJae Park
2022-11-24 18:57 ` [PATCH 07/13] defer/rcuusage: Provide the reference to synchronous RCU update-side primitives SeongJae Park
2022-11-24 18:57 ` [PATCH 08/13] defer/rcuusage: Add a missed unbreakable space SeongJae Park
2022-11-24 18:57 ` SeongJae Park [this message]
2022-11-24 18:58 ` [PATCH 10/13] defer/rcuusage: Fix wrong function name: s/timer_stop/nmi_stop/ SeongJae Park
2022-11-24 18:58 ` [PATCH 11/13] defer/rcurelated: Remove unopen closing parentheses SeongJae Park
2022-11-24 18:58 ` [PATCH 12/13] defer/whichtochoose: Fix a wrongly positioned unbreakable space SeongJae Park
2022-11-24 18:58 ` [PATCH 13/13] defer/whichtochoose: Remove an unnecessary space SeongJae Park
2022-11-24 20:48 ` [PATCH 00/13] Minor fixes for defer/ Paul E. McKenney
2022-11-24 20:56   ` SeongJae Park

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221124185803.8150-11-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox