From: Wei Yang <richard.weiyang@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, rcu@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc/RCU/listRCU: fix an example code snippets
Date: Thu, 23 Jan 2025 01:48:57 +0000 [thread overview]
Message-ID: <20250123014857.fgkmlkpao6q4yax2@master> (raw)
In-Reply-To: <20250101082306.10404-1-richard.weiyang@gmail.com>
Ping
On Wed, Jan 01, 2025 at 08:23:06AM +0000, Wei Yang wrote:
>The example code for "Eliminating Stale Data" looks not correct:
>
> * rcu_read_unlock() should put after kstrdup()
> * spin_unlock() should be called before return
>
>Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>
>---
>Hope my understanding is correct.
>---
> Documentation/RCU/listRCU.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>diff --git a/Documentation/RCU/listRCU.rst b/Documentation/RCU/listRCU.rst
>index ed5c9d8c9afe..8df50fcd69fd 100644
>--- a/Documentation/RCU/listRCU.rst
>+++ b/Documentation/RCU/listRCU.rst
>@@ -348,9 +348,10 @@ to accomplish this would be to add a ``deleted`` flag and a ``lock`` spinlock to
> rcu_read_unlock();
> return AUDIT_BUILD_CONTEXT;
> }
>- rcu_read_unlock();
> if (state == AUDIT_STATE_RECORD)
> *key = kstrdup(e->rule.filterkey, GFP_ATOMIC);
>+ spin_unlock(&e->lock);
>+ rcu_read_unlock();
> return state;
> }
> }
>--
>2.34.1
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-01-23 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 8:23 [PATCH] doc/RCU/listRCU: fix an example code snippets Wei Yang
2025-01-23 1:48 ` Wei Yang [this message]
2025-02-17 2:12 ` Boqun Feng
2025-02-17 2:22 ` Alan Huang
2025-02-17 2:35 ` Boqun Feng
2025-02-17 7:41 ` Wei Yang
2025-02-17 8:02 ` Alan Huang
2025-02-17 9:18 ` Wei Yang
2025-02-17 22:30 ` Boqun Feng
2025-02-18 0:25 ` Wei Yang
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=20250123014857.fgkmlkpao6q4yax2@master \
--to=richard.weiyang@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@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