From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Dipankar Sarma <dipankar@in.ibm.com>,
linux-kernel@vger.kernel.org, adas@redhat.com, hch@lst.de,
npiggin@gmail.com
Subject: Re: rcu: fix hlist_bl_set_first_rcu annotation
Date: Sun, 3 Feb 2013 10:39:58 -0800 [thread overview]
Message-ID: <20130203183958.GO2632@linux.vnet.ibm.com> (raw)
In-Reply-To: <1359572877.2719.50.camel@menhir>
On Wed, Jan 30, 2013 at 07:07:57PM +0000, Steven Whitehouse wrote:
>
> Abhi noticed that we were getting a complaint from the RCU subsystem
> about access of an RCU protected list under the write side bit lock.
> This patch adds additional annotation to check both the RCU read
> lock and the write side bit lock before printing a message.
>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> Reported-by: Abhijith Das <adas@redhat.com>
> Tested-by: Abhijith Das <adas@redhat.com>
Looks plausible to me on first glance, copying Nick Piggin and Christoph
Hellwig. If they have no objections, I will queue this.
Thanx, Paul
> diff --git a/include/linux/list_bl.h b/include/linux/list_bl.h
> index 31f9d75..2eb8855 100644
> --- a/include/linux/list_bl.h
> +++ b/include/linux/list_bl.h
> @@ -125,6 +125,11 @@ static inline void hlist_bl_unlock(struct hlist_bl_head *b)
> __bit_spin_unlock(0, (unsigned long *)b);
> }
>
> +static inline bool hlist_bl_is_locked(struct hlist_bl_head *b)
> +{
> + return bit_spin_is_locked(0, (unsigned long *)b);
> +}
> +
> /**
> * hlist_bl_for_each_entry - iterate over list of given type
> * @tpos: the type * to use as a loop cursor.
> diff --git a/include/linux/rculist_bl.h b/include/linux/rculist_bl.h
> index cf1244f..4f216c5 100644
> --- a/include/linux/rculist_bl.h
> +++ b/include/linux/rculist_bl.h
> @@ -20,7 +20,7 @@ static inline void hlist_bl_set_first_rcu(struct hlist_bl_head *h,
> static inline struct hlist_bl_node *hlist_bl_first_rcu(struct hlist_bl_head *h)
> {
> return (struct hlist_bl_node *)
> - ((unsigned long)rcu_dereference(h->first) & ~LIST_BL_LOCKMASK);
> + ((unsigned long)rcu_dereference_check(h->first, hlist_bl_is_locked(h)) & ~LIST_BL_LOCKMASK);
> }
>
> /**
>
>
next prev parent reply other threads:[~2013-02-03 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 19:07 rcu: fix hlist_bl_set_first_rcu annotation Steven Whitehouse
2013-02-03 18:39 ` Paul E. McKenney [this message]
2013-02-15 0:01 ` Andrew Price
2013-02-15 0:47 ` Paul E. McKenney
2013-03-12 9:44 ` Steven Whitehouse
2013-03-12 12:46 ` Paul E. McKenney
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=20130203183958.GO2632@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=adas@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).