netdev - Re: [PATCH net-next] vxlan: expose COLLECT

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: <CAEP_g=-7-PkYGdcigXC68nh+nCKHkr=9soYjcQsCx5rOkTQ90Q@mail.gmail.com>
Date:	Mon, 3 Aug 2015 14:14:18 -0700
From:	Jesse Gross <jesse@...ira.com>
To:	Alexei Starovoitov <ast@...mgrid.com>
Cc:	Thomas Graf <tgraf@...g.ch>,
	"David S. Miller" <davem@...emloft.net>,
	Daniel Borkmann <daniel@...earbox.net>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] vxlan: expose COLLECT_METADATA flag to user space

On Fri, Jul 31, 2015 at 8:41 AM, Alexei Starovoitov <ast@...mgrid.com> wrote:
> thanks. I think exposing collect_metadata for vxlan and in the future
> for other tunnel types is the clean enough way, though the other
> alternative would be to get rid of collect_metadata flag
> from the kernel and do it when flowmode flag is set. Thoughts?

This seems like a good idea to me - I'm not sure that flow based
tunnels are all that useful without metadata collection enabled and
the fewer interfaces that we have to create for each tunnel type, the
better.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html