netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@mellanox.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, andy@greyhouse.net, mlxsw@mellanox.com
Subject: Re: [PATCH net] ipv6: Do not consider linkdown nexthops during multipath
Date: Tue, 21 Nov 2017 12:00:03 -0700	[thread overview]
Message-ID: <77e45cd4-48a9-71f8-19dc-93b44ebb14b9@gmail.com> (raw)
In-Reply-To: <20171121075012.11077-1-idosch@mellanox.com>

On 11/21/17 12:50 AM, Ido Schimmel wrote:
> When the 'ignore_routes_with_linkdown' sysctl is set, we should not
> consider linkdown nexthops during route lookup.
> 
> While the code correctly verifies that the initially selected route
> ('match') has a carrier, it does not perform the same check in the
> subsequent multipath selection, resulting in a potential packet loss.
> 
> In case the chosen route does not have a carrier and the sysctl is set,
> choose the initially selected route.
> 
> Fixes: 35103d11173b ("net: ipv6 sysctl option to ignore routes when nexthop link is down")
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> ---
>  net/ipv6/route.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index 05eb7bc36156..0363db914c7a 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -472,6 +472,11 @@ static struct rt6_info *rt6_multipath_select(struct rt6_info *match,
>  				&match->rt6i_siblings, rt6i_siblings) {
>  			route_choosen--;
>  			if (route_choosen == 0) {
> +				struct inet6_dev *idev = sibling->rt6i_idev;
> +
> +				if (!netif_carrier_ok(sibling->dst.dev) &&
> +				    idev->cnf.ignore_routes_with_linkdown)
> +					break;
>  				if (rt6_score_route(sibling, oif, strict) < 0)
>  					break;
>  				match = sibling;
> 

Looks right to me.

Acked-by: David Ahern <dsahern@gmail.com>

  reply	other threads:[~2017-11-21 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  7:50 [PATCH net] ipv6: Do not consider linkdown nexthops during multipath Ido Schimmel
2017-11-21 19:00 ` David Ahern [this message]
2017-11-21 19:11 ` Andy Gospodarek
2017-11-23 16:27 ` 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=77e45cd4-48a9-71f8-19dc-93b44ebb14b9@gmail.com \
    --to=dsahern@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=idosch@mellanox.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).