From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Stephen Hemminger <stephen@networkplumber.org>,
lttng-dev@lists.lttng.org, sparse@chrisli.org,
linux-sparse@vger.kernel.org
Subject: Re: [RFC] adding into middle of RCU list
Date: Sat, 31 Aug 2013 14:32:28 -0700 [thread overview]
Message-ID: <20130831213228.GF3871@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130830021637.GA21862@leaf>
On Thu, Aug 29, 2013 at 07:16:37PM -0700, Josh Triplett wrote:
> On Thu, Aug 29, 2013 at 05:57:33PM -0700, Paul E. McKenney wrote:
> > On Fri, Aug 23, 2013 at 02:08:22PM -0700, Paul E. McKenney wrote:
> > > On Fri, Aug 23, 2013 at 01:16:53PM -0400, Mathieu Desnoyers wrote:
> > > > #define __rcu_assign_pointer(p, v, space) \
> > > > do { \
> > > > smp_wmb(); \
> > > > (p) = (typeof(*v) __force space *)(v); \
> > > > } while (0)
> > >
> > > Or I need to fix this one as well. ;-)
> >
> > In that vein... Is there anything like typeof() that also preserves
> > sparse's notion of address space? Wrapping an ACCESS_ONCE() around
> > "p" in the assignment above results in sparse errors.
>
> typeof() will preserve sparse's notion of address space as long as you
> do typeof(p), not typeof(*p):
>
> $ cat test.c
> #define as(n) __attribute__((address_space(n),noderef))
> #define __force __attribute__((force))
>
> int main(void)
> {
> int target = 0;
> int as(1) *foo = (__force typeof(target) as(1) *) ⌖
> typeof(foo) bar = foo;
> return *bar;
> }
> $ sparse test.c
> test.c:9:13: warning: dereference of noderef expression
>
> Notice that sparse didn't warn on the assignment of foo to bar (because
> typeof propagated the address space of 1), and warned on the dereference
> of bar (because typeof propagated noderef).
Thank you for the info!
Suppose that I want to do something like this:
#define __rcu_assign_pointer(p, v, space) \
do { \
smp_wmb(); \
ACCESS_ONCE(p) = (typeof(*v) __force space *)(v); \
} while (0)
Now, this does typeof(*p), so as you noted above sparse complains about
address-space mismatches. Thus far, I haven't been able to come up with
something that (1) does sparse address-space checking, (2) does C type
checking, and (3) forces the assignment to be volatile.
Any thoughts on how to do this?
Thanx, Paul
next prev parent reply other threads:[~2013-08-31 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130822213318.49a57fa2@nehalam.linuxnetplumber.net>
[not found] ` <20130823164637.GB3871@linux.vnet.ibm.com>
[not found] ` <20130823171653.GA16558@Krystal>
[not found] ` <20130823210822.GD3871@linux.vnet.ibm.com>
2013-08-30 0:57 ` [RFC] adding into middle of RCU list Paul E. McKenney
2013-08-30 2:16 ` Josh Triplett
2013-08-31 21:32 ` Paul E. McKenney [this message]
2013-09-01 20:42 ` Josh Triplett
2013-09-01 22:26 ` Paul E. McKenney
2013-09-01 22:43 ` Josh Triplett
2013-09-01 23:42 ` [PATCH] rcu: Make rcu_assign_pointer's assignment volatile and type-safe Josh Triplett
2013-09-02 2:01 ` 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=20130831213228.GF3871@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=sparse@chrisli.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).