netdev - Re: [PATCH net-next 2/4] ipv6: Use a 31-bit multipath hash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5a3e26ec-8dee-fb88-5ad1-7329609cfab3@gmail.com>
Date:   Tue, 9 Jan 2018 20:43:52 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...lanox.com>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, roopa@...ulusnetworks.com,
        nikolay@...ulusnetworks.com, pch@...bogen.com, jkbs@...hat.com,
        yoshfuji@...ux-ipv6.org, mlxsw@...lanox.com
Subject: Re: [PATCH net-next 2/4] ipv6: Use a 31-bit multipath hash

On 1/9/18 7:40 AM, Ido Schimmel wrote:
> The hash thresholds assigned to IPv6 nexthops are in the range of
> [-1, 2^31 - 1], where a negative value is assigned to nexthops that
> should not be considered during multipath selection.
> 
> Therefore, in a similar fashion to IPv4, we need to use the upper
> 31-bits of the multipath hash for multipath selection.
> 
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> ---
>  net/ipv6/route.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

Acked-by: David Ahern <dsahern@...il.com>