netdev - Re: [PATCH net-next v3 0/3] NSH and VxLAN-GPE

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, 1 Mar 2016 10:12:34 -0800
From:	Alexei Starovoitov <alexei.starovoitov@...il.com>
To:	Brian Russell <brussell@...cade.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/3] NSH and VxLAN-GPE

On Tue, Mar 01, 2016 at 11:11:46AM +0000, Brian Russell wrote:
> These patches add a new module to support encap/decap of Network
> Service Header (NSH) as defined in:
> 
> https://tools.ietf.org/html/draft-ietf-sfc-nsh-01
> 
> Both NSH Type 1 and Type 2 metadata are supported with a simple registration
> hook to allow listeners to register to see packets with Type 1 or a specific
> class of Type 2 metadata. NSH could be added to packets sent over a variety
> of link types, eg. VxLAN, GRE, ethernet.
> 
> v2 - fix copyright notices and tidy up use of types
> 
> v3 - fix various style issues in nsh module
>      remove VxLAN-GPE changes
>      add nsh logging module as example
>      add nsh netfilter encap target as example

two fake examples are trying to justify EXPORT_SYMBOL(nsh_register_listener) ?!
what's the real meaning of this patch set?
As far as I can see in-tree users cannot do anything useful with it.