netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@mellanox.com>
To: David Ahern <dsahern@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jiri Pirko <jiri@mellanox.com>,
	Saeed Mahameed <saeedm@mellanox.com>,
	David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH net-next 02/13] ipv4: Move IN_DEV_IGNORE_ROUTES_WITH_LINKDOWN to helper
Date: Wed, 27 Mar 2019 07:44:43 +0000	[thread overview]
Message-ID: <20190327074441.GB12504@splinter> (raw)
In-Reply-To: <20190327032942.20473-3-dsahern@kernel.org>

On Tue, Mar 26, 2019 at 08:29:31PM -0700, David Ahern wrote:
> From: David Ahern <dsahern@gmail.com>
> 
> in_dev lookup followed by IN_DEV_IGNORE_ROUTES_WITH_LINKDOWN check
> is called in several places, some with the rcu lock and others with the
> rtnl held.
> 
> Move the check to a helper similar to what IPv6 has. Since the helper
> can be invoked from either context use rcu_dereference_rtnl to
> dereference ip_ptr.
> 
> Signed-off-by: David Ahern <dsahern@gmail.com>

Reviewed-by: Ido Schimmel <idosch@mellanox.com>

See one nit below.

> ---
>  include/linux/inetdevice.h | 14 ++++++++++++++
>  net/ipv4/fib_semantics.c   | 31 +++++++------------------------
>  net/ipv4/fib_trie.c        |  4 +---
>  3 files changed, 22 insertions(+), 27 deletions(-)
> 
> diff --git a/include/linux/inetdevice.h b/include/linux/inetdevice.h
> index a64f21a97369..35e0390fd7b8 100644
> --- a/include/linux/inetdevice.h
> +++ b/include/linux/inetdevice.h
> @@ -237,6 +237,20 @@ static inline struct in_device *__in_dev_get_rtnl(const struct net_device *dev)
>  	return rtnl_dereference(dev->ip_ptr);
>  }
>  
> +/* called with rc_read_lock or rtnl held */

s/rc_read_lock/rcu_read_lock/

> +static inline bool ip_ignore_linkdown(const struct net_device *dev)
> +{
> +	struct in_device *in_dev;
> +	bool rc = false;
> +
> +	in_dev = rcu_dereference_rtnl(dev->ip_ptr);
> +	if (in_dev &&
> +	    IN_DEV_IGNORE_ROUTES_WITH_LINKDOWN(in_dev))
> +		rc = true;
> +
> +	return rc;
> +}

  reply	other threads:[~2019-03-27  7:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  3:29 [PATCH net-next 00/13] net: Move fib_nh and fib6_nh to a common struct David Ahern
2019-03-27  3:29 ` [PATCH net-next 01/13] ipv4: Define fib_get_nhs when CONFIG_IP_ROUTE_MULTIPATH is disabled David Ahern
2019-03-27  7:40   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 02/13] ipv4: Move IN_DEV_IGNORE_ROUTES_WITH_LINKDOWN to helper David Ahern
2019-03-27  7:44   ` Ido Schimmel [this message]
2019-03-27  3:29 ` [PATCH net-next 03/13] ipv4: Create init helper for fib_nh David Ahern
2019-03-27  8:12   ` Ido Schimmel
2019-03-27 14:17     ` David Ahern
2019-03-27  3:29 ` [PATCH net-next 04/13] ipv4: Create cleanup " David Ahern
2019-03-27  8:17   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 05/13] ipv6: Create init helper for fib6_nh David Ahern
2019-03-27  8:34   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 06/13] ipv6: Create cleanup " David Ahern
2019-03-27  8:38   ` Ido Schimmel
2019-03-27 14:17     ` David Ahern
2019-03-27  3:29 ` [PATCH net-next 07/13] ipv6: Move gateway checks to a fib6_nh setting David Ahern
2019-03-27  9:08   ` Ido Schimmel
2019-03-27 14:21     ` David Ahern
2019-03-27  3:29 ` [PATCH net-next 08/13] ipv6: Refactor fib6_ignore_linkdown David Ahern
2019-03-27  9:19   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 09/13] ipv6: Change rt6_add_nexthop and rt6_nexthop_info to take fib6_nh David Ahern
2019-03-27  9:24   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 10/13] ipv4: Rename fib_nh entries David Ahern
2019-03-27  3:29 ` [PATCH net-next 11/13] ipv6: Rename fib6_nh entries David Ahern
2019-03-27  3:29 ` [PATCH net-next 12/13] net: Add fib_nh_common and update fib_nh and fib6_nh David Ahern
2019-03-27  9:54   ` Ido Schimmel
2019-03-27  3:29 ` [PATCH net-next 13/13] net: Use common nexthop init and release helpers David Ahern
2019-03-27  9:46   ` Ido Schimmel
2019-03-27 14:22     ` David Ahern

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=20190327074441.GB12504@splinter \
    --to=idosch@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.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).