From: "Suzanne Wood" <suzannew@cs.pdx.edu>
To: <linux-kernel@vger.kernel.org>
Cc: <SteveW@ACM.org>, <paulmck@us.ibm.com>, <walpole@cs.pdx.edu>
Subject: rcu read-side protection
Date: Tue, 16 Aug 2005 17:09:29 -0700 [thread overview]
Message-ID: <000f01c5a2bf$f8e752d0$6401a8c0@woodworkxi42l4> (raw)
In dn_neigh_construct() of linux-2.6.12/net/decnet/dn_neigh.c
static int dn_neigh_construct(struct neighbour *neigh)
{
struct net_device *dev = neigh->dev;
struct dn_neigh *dn = (struct dn_neigh *)neigh;
struct dn_dev *dn_db;
struct neigh_parms *parms;
rcu_read_lock();
dn_db = rcu_dereference(dev->dn_ptr);
if (dn_db == NULL) {
rcu_read_unlock();
return -EINVAL;
}
parms = dn_db->neigh_parms;
if (!parms) {
rcu_read_unlock();
return -EINVAL;
}
__neigh_parms_put(neigh->parms);
neigh->parms = neigh_parms_clone(parms);
rcu_read_unlock();
if (dn_db->use_long)
neigh->ops = &dn_long_ops;
else
neigh->ops = &dn_short_ops;
if (dn->flags & DN_NDFLAG_P3)
neigh->ops = &dn_phase3_ops;
neigh->nud_state = NUD_NOARP;
neigh->output = neigh->ops->connected_output;
if ((dev->type == ARPHRD_IPGRE) || (dev->flags & IFF_POINTOPOINT))
memcpy(neigh->ha, dev->broadcast, dev->addr_len);
else if ((dev->type == ARPHRD_ETHER) || (dev->type == ARPHRD_LOOPBACK))
dn_dn2eth(neigh->ha, dn->addr);
else {
if (net_ratelimit())
printk(KERN_DEBUG "Trying to create neigh for hw %d\n", dev->type);
return -EINVAL;
}
A read-side critical section is marked to protect the dereference of the
dn_ptr and assignment to dn_db which is a pointer to a dn_dev. (struct
net_device is defined in /linux/netdevice.h and its dn_ptr in
/include/net/dn_dev.h) Should this rcu-protection be extended to the line
following rcu_read_lock()? Even though use_long is a simple char, it
appears to be a member of an rcu-protected structure.
Thank you.
next reply other threads:[~2005-08-17 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 0:09 Suzanne Wood [this message]
2005-08-17 2:01 ` Paul E. McKenney
2005-08-17 8:25 ` Steven Whitehouse
2005-08-17 14:14 ` Paul E. McKenney
2005-08-17 14:45 ` Steven Whitehouse
2005-08-17 15:21 ` Patrick Caulfield
2005-08-17 19:05 ` David S. Miller
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='000f01c5a2bf$f8e752d0$6401a8c0@woodworkxi42l4' \
--to=suzannew@cs.pdx.edu \
--cc=SteveW@ACM.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=walpole@cs.pdx.edu \
/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
all inboxes | Powered by JetHome®