netdev - Re: [PATCH/RFC net-next 0/3] introduce Geneve options support in TC tunnel key

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]

Date:   Tue, 6 Mar 2018 18:16:38 +0100
From:   Simon Horman <simon.horman@...ronome.com>
To:     Or Gerlitz <gerlitz.or@...il.com>
Cc:     Jiri Pirko <jiri@...lanox.com>,
        Jamal Hadi Salim <jhs@...atatu.com>,
        Cong Wang <xiyou.wangcong@...il.com>,
        Linux Netdev List <netdev@...r.kernel.org>,
        oss-drivers@...ronome.com
Subject: Re: [PATCH/RFC net-next 0/3] introduce Geneve options support in TC
 tunnel key

On Tue, Mar 06, 2018 at 07:11:12PM +0200, Or Gerlitz wrote:
> On Tue, Mar 6, 2018 at 7:08 PM, Simon Horman <simon.horman@...ronome.com> wrote:
> > Hi all,
> >
> > This set adds Geneve options support to the TC tunnel key action.
> > Options TLVs are exposed to userspace using a list of netlink attributes
> > with each option described using attributes for class, type and data.
> 
> can you comment re what are the change vs your earlier post (will
> appreciate an arch link to the thread..)

The main change is that the netlink interface exposes netlink attribute for
the class, type and data of each option, rather than a single attribute
that describes all options as a byte-string.

I believe the previous discussion is here:
https://www.spinics.net/lists/netdev/msg457058.html