linux-kernel - Re: [net-next] seg6: allow local packet processing for SRv6 End.DT6 behavior

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20191119.152238.234909279065487800.davem@davemloft.net>
Date:   Tue, 19 Nov 2019 15:22:38 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     andrea.mayer@...roma2.it
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
        dav.lebrun@...il.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [net-next] seg6: allow local packet processing for SRv6
 End.DT6 behavior

From: Andrea Mayer <andrea.mayer@...roma2.it>
Date: Mon, 18 Nov 2019 19:20:26 +0100

> End.DT6 behavior makes use of seg6_lookup_nexthop() function which drops
> all packets that are destined to be locally processed. However, DT* should
> be able to delivery decapsulated packets that are destined to local
> addresses. Function seg6_lookup_nexthop() is also used by DX6, so in order
> to maintain compatibility I created another routing helper function which
> is called seg6_lookup_any_nexthop(). This function is able to take into
> account both packets that have to be processed locally and the ones that
> are destined to be forwarded directly to another machine. Hence,
> seg6_lookup_any_nexthop() is used in DT6 rather than seg6_lookup_nexthop()
> to allow local delivery.
> 
> Signed-off-by: Andrea Mayer <andrea.mayer@...roma2.it>

Please address Sergei's feedback and resubmit, thank you.