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  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:	Tue, 4 Aug 2015 21:07:52 -0700
From:	Alexei Starovoitov <>
To:	Pravin Shelar <>
Cc:	netdev <>
Subject: Re: [PATCH net-next v3 2/3] openvswitch: Use regular GRE net_device
 instead of vport

On Tue, Aug 04, 2015 at 07:50:40PM -0700, Pravin Shelar wrote:
> I am planning on adding the ip_gre netlink interface later on. OVS
> userspace needs same interface to directly create the GRE device
> without vport-gre module. vport-gre module is compatibility code. If
> you want I can do it in same patch.

I think it has to be part of the same patch set especially if ovs
userspace is going to create gre netdev directly.
Adding IFLA_GRE_COLLECT_METADATA flag will let anyone use this gre tunnel
with normal routing that already understands tunnel metadata and
if routing is working then bpf helpers will work with it seamlessly as well.

Have another question:
+ info->key.tun_flags = tpi->flags & (TUNNEL_CSUM | TUNNEL_KEY);
why keep CSUM flag ?
Current ip_tunnel_key doesn't have csum field, so gre csum gets lost
after decap anyway?

Also I think FLOWBASED is a bad name both here and in vxlan.
Tunnel that understands metadata on tx/rx has nothing to do with flows.
into one IFLA_VXLAN_COLLECT_METADATA while it's not too late.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists