netdev - Re: [PATCH net-next v3 2/2] net: ipv6: ioam6: new feature tunsrc

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: <e15e5b9e-e392-4cf4-8620-9bcc375711b1@redhat.com>
Date: Thu, 22 Aug 2024 10:44:43 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Justin Iurman <justin.iurman@...ege.be>, netdev@...r.kernel.org
Cc: davem@...emloft.net, dsahern@...nel.org, edumazet@...gle.com,
 kuba@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3 2/2] net: ipv6: ioam6: new feature tunsrc

On 8/17/24 15:18, Justin Iurman wrote:
> This patch provides a new feature (i.e., "tunsrc") for the tunnel (i.e.,
> "encap") mode of ioam6. Just like seg6 already does, except it is
> attached to a route. The "tunsrc" is optional: when not provided (by
> default), the automatic resolution is applied. Using "tunsrc" when
> possible has a benefit: performance. See the comparison:
>   - before (= "encap" mode): https://ibb.co/bNCzvf7
>   - after (= "encap" mode with "tunsrc"): https://ibb.co/PT8L6yq

Please note that Jakub's question about self-tests still stands off.

I think the easier path for that goal is to have this patch merged, and 
than the iproute counter-part, and finally adds the related functional 
tests (you will need to probe the kernel and iproute features), but 
please follow-up on that, thanks!

Paolo