From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next-2.6] bridge: add __rcu annotations
Date: Sat, 13 Nov 2010 18:58:50 +0100 [thread overview]
Message-ID: <1289671130.2743.28.camel@edumazet-laptop> (raw)
In-Reply-To: <20101113093545.6fe9c077@nehalam>
Le samedi 13 novembre 2010 à 09:35 -0800, Stephen Hemminger a écrit :
> On Sat, 13 Nov 2010 09:15:28 +0100
> Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> > index 578debb..ffbd177 100644
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -996,7 +996,10 @@ struct net_device {
> > #endif
> >
> > rx_handler_func_t *rx_handler;
> > - void *rx_handler_data;
> > + union {
> > + void *rx_handler_data;
> > + struct net_bridge_port __rcu *br_port_rcu;
> > + };
> >
> > struct netdev_queue __rcu *ingress_queue;
>
> I don't like making the generic hook typed again.
> We don't do this for other callbacks, timers, workqueues, ...
> Why is it necessary for RCU notation.
>
because rcu_dereference() needs the type for __CHECKER__/sparse checks
#define __rcu_dereference_check(p, c, space) \
({ \
typeof(*p) *_________p1 = (typeof(*p)*__force )ACCESS_ONCE(p); \
rcu_lockdep_assert(c); \
rcu_dereference_sparse(p, space); \
smp_read_barrier_depends(); \
((typeof(*p) __force __kernel *)(_________p1)); \
})
So using a "void *ptr" is not an option
Its also cleaner to use
rcu_dereference(dev->br_port_rcu)
instead of
(struct net_bridge_port *)rcu_dereference(dev->rx_handler_data)
next prev parent reply other threads:[~2010-11-13 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 8:15 [PATCH net-next-2.6] bridge: add __rcu annotations Eric Dumazet
2010-11-13 17:35 ` Stephen Hemminger
2010-11-13 17:58 ` Eric Dumazet [this message]
2010-11-13 18:13 ` Stephen Hemminger
2010-11-13 22:04 ` Eric Dumazet
2010-11-14 18:47 ` Stephen Hemminger
2010-11-16 12:59 ` Simon Horman
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=1289671130.2743.28.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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