[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <17c80bc2aba.fa4204331209995.6054034489659150411@shytyi.net>
Date: Thu, 14 Oct 2021 23:36:27 +0200
From: Dmytro Shytyi <dmytro@...tyi.net>
To: "Erik Kline" <ek@...gle.com>
Cc: "Jakub Kicinski" <kuba@...nel.org>,
"yoshfuji" <yoshfuji@...ux-ipv6.org>,
"kuznet" <kuznet@....inr.ac.ru>,
"liuhangbin" <liuhangbin@...il.com>, "davem" <davem@...emloft.net>,
"netdev" <netdev@...r.kernel.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"Jscherpelz" <jscherpelz@...gle.com>
Subject: Re: [PATCH net-next V10] net: Variable SLAAC: SLAAC with prefixes
of arbitrary length in PIO
> > This patch solves "Race to the bottom" problem in VSLAAC.
>
> How exactly does this "solve" the fundamental problem?
>
VSLAAC is replaced by the SLAAC starting from /64
if (pinfo->prefix_len == 64) {
64_bit_addr_gen
} else if (pinfo->prefix_len > 0 && pinfo->prefix_len < 64 &&
in6_dev->cnf.variable_slaac) {
variable_bit_addr_gen
} else {
net_dbg_ratelimited("IPv6: Prefix with unexpected length %d\n",
pinfo->prefix_len);
}
I meant to say that this is no longer an issue in VSLAAC particular context, considering /128 bits the "bottom".
In this version of the patch, we are not reaching the /128 bit "bottom".
Best regards,
Dmytro SHYTYI.
Powered by blists - more mailing lists