netdev - Re: [PATCH net-next 4/5] ipv6: Compute multipath hash for sent ICMP errors from offending packet

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: <95fdee03-d595-f1fd-b10d-fc775feaef2b@stressinduktion.org>
Date:   Mon, 24 Oct 2016 11:40:39 +0200
From:   Hannes Frederic Sowa <hannes@...essinduktion.org>
To:     Jakub Sitnicki <jkbs@...hat.com>, netdev@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        "David S. Miller" <davem@...emloft.net>,
        Alexey Kuznetsov <kuznet@....inr.ac.ru>,
        James Morris <jmorris@...ei.org>,
        Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
        Patrick McHardy <kaber@...sh.net>,
        Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next 4/5] ipv6: Compute multipath hash for sent ICMP
 errors from offending packet

On 24.10.2016 11:28, Jakub Sitnicki wrote:
> Improve debuggability with tools like traceroute and make PMTUD work in
> setups that make use of ECMP routing by sending ICMP errors down the
> same path as the offending packet would travel, if it was going in the
> opposite direction.
> 
> There is a caveat, flows in both directions need use the same
> label. Otherwise packets from flow in the opposite direction and ICMP
> errors will not be routed over the same ECMP link.
> 
> Export the function for calculating the multipath hash so that we can
> use it also on receive side, when forwarding ICMP errors.
> 
> Signed-off-by: Jakub Sitnicki <jkbs@...hat.com>

Acked-by: Hannes Frederic Sowa <hannes@...essinduktion.org>