netdev - Re: [PATCH iproute2-next v2 0/2] ip/tunnel: Unify collect metadata handling

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] [day] [month] [year] [list]

Date:   Wed, 24 Jan 2018 11:05:17 -0700
From:   David Ahern <dsahern@...il.com>
To:     Serhey Popovych <serhe.popovych@...il.com>, netdev@...r.kernel.org
Cc:     jbenc@...hat.com, pabeni@...hat.com, u9012063@...il.com,
        julien@...ulusnetworks.com
Subject: Re: [PATCH iproute2-next v2 0/2] ip/tunnel: Unify collect metadata
 handling

On 1/22/18 10:23 AM, Serhey Popovych wrote:
> With this series I want to unify collect metadata
> handling in tunnels:
> 
>   1) Use "external" name for JSON and non-JSON output.
> 
>      Do not *print* any options when tunnel in
>      collect metadata mode: gre6 already do
>      this, so just apply to others.
> 
>   2) Do not *add* any attributes when configuring
>      gre tunnel in collect metadata mode.
> 
>      Other tunnels (e.g. gre6, iptnl, ip6tnl)
>      alredy do that.
> 
> This is next step in ipv4 and ipv6 modules
> unification to prepare for merge in the future.
> 
> Any comments, suggestions and criticism as always
> welcome.
> 
> v2
>   For all tunnels implementing collect metadata
>   use "external" keyword for both JSON. Thanks
>   to Jiri Benc for detailed explanation.
> 

Series applied to iproute2-next