From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: hideaki.yoshifuji@miraclelinux.com,
network dev <netdev@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCHv3] net/ipv6: add sysctl option accept_ra_min_hop_limit
Date: Thu, 30 Jul 2015 09:45:26 +0900 [thread overview]
Message-ID: <55B973A6.1060607@miraclelinux.com> (raw)
In-Reply-To: <CAPwn2JT6e=f0q=Q5rbqF_6ZejLyj+Ysyk1eP5KTBkGLz-Mpfqg@mail.gmail.com>
Hi,
Hangbin Liu wrote:
>>> diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
>>> index 0a05b35..acda056 100644
>>> --- a/net/ipv6/ndisc.c
>>> +++ b/net/ipv6/ndisc.c
>>> @@ -1226,13 +1226,11 @@ static void ndisc_router_discovery(struct sk_buff *skb)
>>> if (rt)
>>> rt6_set_expires(rt, jiffies + (HZ * lifetime));
>>> if (ra_msg->icmph.icmp6_hop_limit) {
>>> - /* Only set hop_limit on the interface if it is higher than
>>> - * the current hop_limit.
>>> - */
>>> - if (in6_dev->cnf.hop_limit < ra_msg->icmph.icmp6_hop_limit) {
>>> + if (in6_dev->cnf.accept_ra_min_hop_limit <= ra_msg->icmph.icmp6_hop_limit &&
>>> + ra_msg->icmph.icmp6_hop_limit != 0) {
>>> in6_dev->cnf.hop_limit = ra_msg->icmph.icmp6_hop_limit;
>>> } else {
>>> - ND_PRINTK(2, warn, "RA: Got route advertisement with lower hop_limit than current\n");
>>> + ND_PRINTK(2, warn, "RA: Got route advertisement with lower hop_limit than minimum\n");
>>> }
>>> if (rt)
>>> dst_metric_set(&rt->dst, RTAX_HOPLIMIT,
>>>
>>
>> Please see my comments against your previous patch.
>
> I pasted you comments here so we don't need to discuss in two mails :)
>
>>
>> ra_msg->icmph.icmp6_hop_limit != 0 is checkd by outer "if".
>
> Yes, thanks for your reminding :)
>
>>
>> You do not need to update cnf.hop_limit if it is already equal to
>> hop limit received.
>
> We need to update cnf.hop_limit if min_hop_limit <= icmp6_hop_limit. e.g.
> current hop limit is 64, min hop limit is 1 and ra hop limit is 32, then we need
> update current hop limit to 32.
OK
>
>>
>> How about ignoring hop limit without message is configured value is
>> larger than 255, BTW?
>
> Although set accept_ra_min_hop_limit great than 255 is meaningless, there
> is also no need to check it since icmp6_hop_limit will not larger than 255. so
>
> + if (in6_dev->cnf.accept_ra_min_hop_limit <= 255 &&
> + in6_dev->cnf.accept_ra_min_hop_limit <=
> ra_msg->icmph.icmp6_hop_limit )
> in6_dev->cnf.hop_limit = ra_msg->icmph.icmp6_hop_limit;
>
> is duplicated check. How do you think?
How about checking in6_dev->cnf.accept_ra_min_hop_limit by outer if, then?
if (in6_dev->cnf.accept_ra_min_hop_limit < 256 &&
ra_msg->icmph.icmp6_hop_limit) {
...
}
>
>>
>>> if (rt)
>>> dst_metric_set(&rt->dst, RTAX_HOPLIMIT,
>>>
>>
>> This can be inside the inner "if".
>
> OK, will move it.
>
>
> Best Regards
> Hangbin
>
Regards,
--
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux.com>
Technical Division, MIRACLE LINUX CORPORATION
next prev parent reply other threads:[~2015-07-30 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 10:14 [PATCHv3] net/ipv6: add sysctl option accept_ra_min_hop_limit Hangbin Liu
2015-07-29 10:39 ` YOSHIFUJI Hideaki
2015-07-29 14:46 ` Hangbin Liu
2015-07-30 0:45 ` YOSHIFUJI Hideaki [this message]
2015-07-30 2:31 ` Hangbin Liu
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=55B973A6.1060607@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux.com \
--cc=hannes@stressinduktion.org \
--cc=liuhangbin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.