From: Kunwu Chan <kunwu.chan@linux.dev>
To: perfbook@vger.kernel.org
Cc: paulmck@kernel.org, Kunwu Chan <kunwu.chan@linux.dev>
Subject: [PATCH] defer/rcuusage: Fix spin_lock arg and write-side term
Date: Tue, 24 Feb 2026 15:53:14 +0800 [thread overview]
Message-ID: <20260224075314.2543888-1-kunwu.chan@linux.dev> (raw)
Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
defer/rcuusage.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/rcuusage.tex b/defer/rcuusage.tex
index b5111043..6c960a00 100644
--- a/defer/rcuusage.tex
+++ b/defer/rcuusage.tex
@@ -1254,7 +1254,7 @@ rcu_read_lock();
list_for_each_entry_rcu(p, &head, list_field) {
do_something_with(p);
if (need_update(p)) {
- spin_lock(my_lock);
+ spin_lock(&my_lock);
do_update(p);
spin_unlock(&my_lock);
}
@@ -1583,7 +1583,7 @@ constraints:
\begin{enumerate}
\item Write-side acquisitions wait for any read-holders to release
the lock.
-\item Writer-side acquisitions wait for any write-holder to release
+\item Write-side acquisitions wait for any write-holder to release
the lock.
\item Read-side acquisitions wait for any write-holder to release
the lock.
--
2.25.1
reply other threads:[~2026-02-24 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260224075314.2543888-1-kunwu.chan@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
/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