From: Jiri Benc <jbenc@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH net-next] ipv6: router reachability probing
Date: Tue, 10 Dec 2013 22:01:44 +0100 [thread overview]
Message-ID: <20131210220144.183982cd@griffin> (raw)
In-Reply-To: <20131210205101.GA25505@order.stressinduktion.org>
On Tue, 10 Dec 2013 21:51:01 +0100, Hannes Frederic Sowa wrote:
> The reason is that we don't send a neighbour advertisment in FAILED state
> and thus shouldn't accept one. RFC 4861 7.2.5. specifies that we should
> not add a new entry to the neighbour discovery table just because of a
> neighbour advertisment. Because NUD_FAILED is just an artifical state
> to the linux kernel we should treat it like the entry is not existent.
That was the missing piece, thanks!
> The canonical way would be to place this neighbor in the NUD_PROBE state
> in rt6_probe.
Okay, will respin the patch.
> > diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> > index ddb9d41c8eea..147c39f7f70d 100644
> > --- a/net/ipv6/route.c
> > +++ b/net/ipv6/route.c
> > @@ -66,8 +66,9 @@
> > #endif
> >
> > enum rt6_nud_state {
> > - RT6_NUD_FAIL_HARD = -2,
> > - RT6_NUD_FAIL_SOFT = -1,
> > + RT6_NUD_FAIL_HARD = -3,
> > + RT6_NUD_FAIL_PROBE = -2,
> > + RT6_NUD_FAIL_DO_RR = -1,
> > RT6_NUD_SUCCEED = 1
> > };
> >
> > @@ -577,11 +578,13 @@ static inline enum rt6_nud_state rt6_check_neigh(struct rt6_info *rt)
> > #ifdef CONFIG_IPV6_ROUTER_PREF
> > else if (!(neigh->nud_state & NUD_FAILED))
> > ret = RT6_NUD_SUCCEED;
> > + else
> > + ret = RT6_NUD_FAIL_PROBE;
> > #endif
>
> Nit:
> We could now change the declaration of ret in rt6_check_neigh from
> "enum rt6_nud_state ret = RT6_NUD_FAIL_HARD"
> to
> "enum rt6_nud_state ret;" as all cases are covered now.
That's what I originally thought, too, but it's not the case when
CONFIG_IPV6_ROUTER_PREF is not defined and neigh->nud_state != NUD_VALID.
> Otherwise the patch is a nice improvment.
Thanks!
Jiri
--
Jiri Benc
prev parent reply other threads:[~2013-12-10 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:15 [PATCH net-next] ipv6: router reachability probing Jiri Benc
2013-12-10 20:51 ` Hannes Frederic Sowa
2013-12-10 21:01 ` Jiri Benc [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=20131210220144.183982cd@griffin \
--to=jbenc@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).