netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
	"Florian Westphal" <fw@strlen.de>,
	"network dev" <netdev@vger.kernel.org>,
	吉藤英明 <hideaki.yoshifuji@miraclelinux.com>
Subject: Re: [PATCH net-next] Revert "net/ipv6: add sysctl option accept_ra_min_hop_limit"
Date: Thu, 10 Sep 2015 11:19:04 +0200	[thread overview]
Message-ID: <20150910091904.GA22575@bistromath.redhat.com> (raw)
In-Reply-To: <CAPwn2JRcHBSj4mnYZyjmYinpcb9yB6Makcw+ynSyMaQJg0cYaQ@mail.gmail.com>

Hello,

2015-09-10, 10:54:38 +0800, Hangbin Liu wrote:
> > Can we still modify the behavior of this sysctl? It's already been in
> > Linus's tree for a while, but if we can, I would rather restrict the
> > values we let the user write to accept_ra_min_hop_limit, as anything
> > outside [0..255] does not really make sense.
> 
> Yes, so the checked if (in6_dev->cnf.accept_ra_min_hop_limit < 256 &&
> ra_msg->icmph.icmp6_hop_limit)  make sure we only update the value between
> [1..255].

I was thinking of returning -EINVAL when the user tries to set it to
300, using proc_dointvec_minmax.


> > Allowing an RA to update the hop limit if
> >
> >    current hop limit < RA.hop_limit < accept_ra_min_hop_limit
> >
> > might also be desirable, but I'm not so sure about this case.
> 
> Yes, and we also should allow an RA to update the hop limit if
> 
> accept_ra_min_hop_limit <= RA.hop_limit < current hop limit
> 
> e.g accept_ra_min_hop_limit = RA.hop_limit =64, current hop limit = 128

Yes, that's what we're doing at the moment, and I would leave it as is.


Thanks,

-- 
Sabrina

  reply	other threads:[~2015-09-10  9:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  9:43 [PATCH net-next] Revert "net/ipv6: add sysctl option accept_ra_min_hop_limit" Sabrina Dubroca
2015-09-02 23:11 ` David Miller
2015-09-03  8:39   ` Florian Westphal
2015-09-09 10:10   ` Sabrina Dubroca
2015-09-10  2:54     ` Hangbin Liu
2015-09-10  9:19       ` Sabrina Dubroca [this message]
2015-09-11  1:29         ` Hangbin Liu
2015-09-10  5:52     ` YOSHIFUJI Hideaki
2015-09-10  9:40       ` Sabrina Dubroca
2015-09-11  3:08         ` YOSHIFUJI Hideaki
2015-09-11 10:53           ` Florian Westphal
2015-09-11 11:09             ` D.S. Ljungmark

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=20150910091904.GA22575@bistromath.redhat.com \
    --to=sd@queasysnail.net \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=hideaki.yoshifuji@miraclelinux.com \
    --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 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).