Linux RCU subsystem development
 help / color / mirror / Atom feed
From: Alan Huang <mmpgouride@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>, Boqun Feng <boqun.feng@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 v2] doc/RCU/listRCU: refine example code for eliminating stale data
Date: Thu, 20 Feb 2025 00:40:20 +0800	[thread overview]
Message-ID: <AB18BC5D-AD55-46DF-939C-44DFA845D168@gmail.com> (raw)
In-Reply-To: <20250218005047.27258-1-richard.weiyang@gmail.com>

On Feb 18, 2025, at 08:50, Wei Yang <richard.weiyang@gmail.com> wrote:
> 
> This patch adjust the example code with following two purpose:
> 
>  * reduce the confusion on not releasing e->lock
>  * emphasize e is valid and not stale with e->lock held
> 
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> CC: Boqun Feng <boqun.feng@gmail.com>
> CC: Alan Huang <mmpgouride@gmail.com>
> 
> ---
> v2:
>  * add the missing parameter *key
>  * make function return struct audit_entry
> ---
> Documentation/RCU/listRCU.rst | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/RCU/listRCU.rst b/Documentation/RCU/listRCU.rst
> index ed5c9d8c9afe..d8bb98623c12 100644
> --- a/Documentation/RCU/listRCU.rst
> +++ b/Documentation/RCU/listRCU.rst
> @@ -334,7 +334,7 @@ If the system-call audit module were to ever need to reject stale data, one way
> to accomplish this would be to add a ``deleted`` flag and a ``lock`` spinlock to the
> ``audit_entry`` structure, and modify audit_filter_task() as follows::
> 
> - static enum audit_state audit_filter_task(struct task_struct *tsk)
> + static struct audit_entry *audit_filter_task(struct task_struct *tsk, char **key)
> {
> struct audit_entry *e;
> enum audit_state   state;
> @@ -346,16 +346,18 @@ to accomplish this would be to add a ``deleted`` flag and a ``lock`` spinlock to
> if (e->deleted) {
> spin_unlock(&e->lock);
> rcu_read_unlock();
> - return AUDIT_BUILD_CONTEXT;
> + return NULL;
> }
> rcu_read_unlock();
> if (state == AUDIT_STATE_RECORD)
> *key = kstrdup(e->rule.filterkey, GFP_ATOMIC);
> - return state;
> + /* As long as e->lock is held, e is valid and
> + * its value is not stale */
> + return e;
> }
> }
> rcu_read_unlock();
> - return AUDIT_BUILD_CONTEXT;
> + return NULL;
> }
> 
> The ``audit_del_rule()`` function would need to set the ``deleted`` flag under the
> -- 
> 2.34.1
> 

I think it’s good enough to illustrate the intention here:

Reviewed-by: Alan Huang <mmpgouride@gmail.com>

Boqun, there is an unreviewed doc patch[1] that fixes the section

 “Using RCU hlist_nulls to protect list and objects”

[1] https://lore.kernel.org/rcu/20240326124431.77430-1-mmpgouride@gmail.com/

: )




  parent reply	other threads:[~2025-02-19 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  0:50 [Patch v2] doc/RCU/listRCU: refine example code for eliminating stale data Wei Yang
2025-02-19 16:00 ` Boqun Feng
2025-02-19 16:40 ` Alan Huang [this message]
2025-03-05 16:40   ` Boqun Feng

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=AB18BC5D-AD55-46DF-939C-44DFA845D168@gmail.com \
    --to=mmpgouride@gmail.com \
    --cc=boqun.feng@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 \
    --cc=richard.weiyang@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