From: Joe Perches <joe@perches.com>
To: Saurabh <saurabh.mohan@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH 01/02] net/ipv4: VTI support rx-path hook in xfrm4_mode_tunnel.
Date: Tue, 17 Jul 2012 13:36:42 -0700 [thread overview]
Message-ID: <1342557402.15318.22.camel@joe2Laptop> (raw)
In-Reply-To: <20120717194449.GA3350@debian-saurabh-64.vyatta.com>
On Tue, 2012-07-17 at 12:44 -0700, Saurabh wrote:
> Incorporated David and Steffen's comments.
> Add hook for rx-path xfmr4_mode_tunnel for VTI tunnel module.
[]
> diff --git a/net/ipv4/xfrm4_mode_tunnel.c b/net/ipv4/xfrm4_mode_tunnel.c
[]
> +int xfrm4_mode_tunnel_input_register(struct xfrm_tunnel *handler)
> +{
> + struct xfrm_tunnel __rcu **pprev;
> + struct xfrm_tunnel *t;
> + int ret = -EEXIST;
> + int priority = handler->priority;
> +
> + mutex_lock(&xfrm4_mode_tunnel_input_mutex);
> +
> + for (pprev = &rcv_notify_handlers;
> + (t = rcu_dereference_protected(*pprev,
> + lockdep_is_held(&xfrm4_mode_tunnel_input_mutex))) != NULL;
> + pprev = &t->next) {
> + if (t->priority > priority)
> + break;
> + if (t->priority == priority)
> + goto err;
> +
> + }
> +
> + handler->next = *pprev;
> + rcu_assign_pointer(*pprev, handler);
> +
> + ret = 0;
> +
> +err:
> + mutex_unlock(&xfrm4_mode_tunnel_input_mutex);
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(xfrm4_mode_tunnel_input_register);
Isn't the multiple indirection of **pprev unnecessary?
Perhaps something like this is simpler and easier to read?
int xfrm4_mode_tunnel_input_register(struct xfrm_tunnel *handler)
{
struct xfrm_tunnel __rcu *prev;
struct xfrm_tunnel *t;
int ret = -EEXIST;
int priority = handler->priority;
mutex_lock(&xfrm4_mode_tunnel_input_mutex);
prev = rcv_notify_handlers;
while ((t = rcu_dereference_protected(prev,
lockdep_is_held(&xfrm4_mode_tunnel_input_mutex))) {
if (t->priority > priority)
break;
if (t->priority == priority)
goto err;
prev = t->next;
}
handler->next = prev;
rcu_assign_pointer(prev, handler);
ret = 0;
err:
mutex_unlock(&xfrm4_mode_tunnel_input_mutex);
return ret;
}
next prev parent reply other threads:[~2012-07-17 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 19:44 [net-next PATCH 01/02] net/ipv4: VTI support rx-path hook in xfrm4_mode_tunnel Saurabh
2012-07-17 20:36 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-29 1:29 Saurabh
2012-06-29 0:52 Saurabh
2012-06-29 1:00 ` David Miller
2012-06-28 1:02 Saurabh
2012-06-08 17:32 Saurabh
2012-06-14 9:25 ` Steffen Klassert
2012-06-15 2:44 ` Saurabh Mohan
2012-06-15 5:46 ` Steffen Klassert
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=1342557402.15318.22.camel@joe2Laptop \
--to=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=saurabh.mohan@vyatta.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).