From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Urs Thuermann <urs@isnogud.escape.de>
Subject: Re: [PATCH net-next-2.6 v2] can: convert protocol handling to RCU
Date: Wed, 6 Apr 2011 11:27:27 +0200 [thread overview]
Message-ID: <20110406092727.GC342@kurt.e-circ.dyndns.org> (raw)
In-Reply-To: <4D9B58EC.9090903@hartkopp.net>
On Tue, Apr 05, 2011 at 08:01:16PM +0200, Oliver Hartkopp wrote:
> This patch removes spin_locks at CAN socket creation time by using RCU.
Good thing.
I'm interested in RCU also for my J1939 code.
I do have some questions below. These are mainly since I'm not yet used
to RCU. Btw, I must have missed v1 of the patch, so I may ask 'already
resolved' things...
>
>
> +static struct can_proto *can_try_module_get(int protocol)
> +{
> + struct can_proto *cp;
> +
> + rcu_read_lock();
> + cp = rcu_dereference(proto_tab[protocol]);
> + if (cp && !try_module_get(cp->prot->owner))
After the xxx_get, is the 'cp' pointer persistent?
> + cp = NULL;
> + rcu_read_unlock();
> +
> + return cp;
> +}
> +
> static int can_create(struct net *net, struct socket *sock, int protocol,
> int kern)
> {
> @@ -130,9 +143,12 @@ static int can_create(struct net *net, struct socket *sock, int protocol,
> if (!net_eq(net, &init_net))
> return -EAFNOSUPPORT;
>
> + cp = can_try_module_get(protocol);
> +
>
[...]
> /* check for available protocol and correct usage */
>
> if (!cp)
> return -EPROTONOSUPPORT;
>
> if (cp->type != sock->type) {
I don't see how this will evaluate to true?
can_proto_register takes care of it.
> - err = -EPROTONOSUPPORT;
> + err = -EPROTOTYPE;
> goto errout;
> }
>
next prev parent reply other threads:[~2011-04-06 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 18:01 [PATCH net-next-2.6 v2] can: convert protocol handling to RCU Oliver Hartkopp
2011-04-06 9:27 ` Kurt Van Dijck [this message]
2011-04-06 14:39 ` Oliver Hartkopp
2011-04-06 15:34 ` Kurt Van Dijck
2011-04-06 19:36 ` David 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=20110406092727.GC342@kurt.e-circ.dyndns.org \
--to=kurt.van.dijck@eia.be \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=urs@isnogud.escape.de \
/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).