From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Doc/RCU: fix pseudocode in rcuref.txt
Date: Wed, 10 Sep 2008 08:40:18 -0700 [thread overview]
Message-ID: <20080910154018.GE6742@linux.vnet.ibm.com> (raw)
In-Reply-To: <48C73873.1010708@cn.fujitsu.com>
On Wed, Sep 10, 2008 at 11:01:07AM +0800, Lai Jiangshan wrote:
>
> atomic_inc_not_zero(v) return 0 if *v = 0.
> use spin_lock instead of write_lock for update lock.
Good catch, Jiangshan, thank you!
Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/Documentation/RCU/rcuref.txt b/Documentation/RCU/rcuref.txt
> index 451de2a..4202ad0 100644
> --- a/Documentation/RCU/rcuref.txt
> +++ b/Documentation/RCU/rcuref.txt
> @@ -29,9 +29,9 @@ release_referenced() delete()
> }
>
> If this list/array is made lock free using RCU as in changing the
> -write_lock() in add() and delete() to spin_lock and changing read_lock
> -in search_and_reference to rcu_read_lock(), the atomic_get in
> -search_and_reference could potentially hold reference to an element which
> +write_lock() in add() and delete() to spin_lock() and changing read_lock()
> +in search_and_reference() to rcu_read_lock(), the atomic_inc() in
> +search_and_reference() could potentially hold reference to an element which
> has already been deleted from the list/array. Use atomic_inc_not_zero()
> in this scenario as follows:
>
> @@ -40,20 +40,20 @@ add() search_and_reference()
> { {
> alloc_object rcu_read_lock();
> ... search_for_element
> - atomic_set(&el->rc, 1); if (atomic_inc_not_zero(&el->rc)) {
> - write_lock(&list_lock); rcu_read_unlock();
> + atomic_set(&el->rc, 1); if (!atomic_inc_not_zero(&el->rc)) {
> + spin_lock(&list_lock); rcu_read_unlock();
> return FAIL;
> add_element }
> ... ...
> - write_unlock(&list_lock); rcu_read_unlock();
> + spin_unlock(&list_lock); rcu_read_unlock();
> } }
> 3. 4.
> release_referenced() delete()
> { {
> - ... write_lock(&list_lock);
> + ... spin_lock(&list_lock);
> if (atomic_dec_and_test(&el->rc)) ...
> call_rcu(&el->head, el_free); delete_element
> - ... write_unlock(&list_lock);
> + ... spin_unlock(&list_lock);
> } ...
> if (atomic_dec_and_test(&el->rc))
> call_rcu(&el->head, el_free);
>
>
prev parent reply other threads:[~2008-09-10 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 3:01 [PATCH] Doc/RCU: fix pseudocode in rcuref.txt Lai Jiangshan
2008-09-10 6:37 ` Ingo Molnar
2008-09-10 15:40 ` Paul E. McKenney
2008-09-10 15:40 ` Paul E. McKenney [this message]
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=20080910154018.GE6742@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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