Netdev List
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Duan Jiong <duanj.fnst@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: host should probe those non-reachable router
Date: Fri, 1 Nov 2013 12:19:57 +0100	[thread overview]
Message-ID: <20131101111957.GA30284@order.stressinduktion.org> (raw)
In-Reply-To: <52731633.2030101@cn.fujitsu.com>

Hi Duan!

On Fri, Nov 01, 2013 at 10:47:15AM +0800, Duan Jiong wrote:
> 
> rather than those routers that the return value of rt6_score_route()
> is RT6_NUD_SUCCEED.
> 
> Signed-off-by: Duan Jiong <duanj.fnst@cn.fujitsu.com>
> ---
>  net/ipv6/route.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index 1ac0b6e..b7bf5c7 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -623,12 +623,11 @@ static struct rt6_info *find_match(struct rt6_info *rt, int oif, int strict,
>  		match_do_rr = true;
>  		m = 0; /* lowest valid score */
>  	} else if (m < 0) {
> +		if (strict & RT6_LOOKUP_F_REACHABLE)
> +			rt6_probe(rt);
>  		goto out;
>  	}
>  
> -	if (strict & RT6_LOOKUP_F_REACHABLE)
> -		rt6_probe(rt);
> -

I don't think this is correct. m < 0 are the routers we really don't want to
use, e.g. because we get a failure signaled from rt6_check_dev. E.g. we want
to query a route where a specified interface id is given.

In case router preference is enabled we mostly give back RT6_NUD_SUCCEED for
routes which are somewhat reachable. Really broken routers in NUD_FAILED state
are waiting for cleanup and recreation. We also do not accept new NAs on
neighbours in NUD_FAILED state IIRC.

Greetings,

  Hannes

      reply	other threads:[~2013-11-01 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  2:47 [PATCH net-next] ipv6: host should probe those non-reachable router Duan Jiong
2013-11-01 11:19 ` Hannes Frederic Sowa [this message]

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=20131101111957.GA30284@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=duanj.fnst@cn.fujitsu.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