netdev - Re: [PATCH v3 net-next 5/8] geneve: Add support to collect tunnel metadata.

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, 25 Aug 2015 19:48:01 +0200
From:	Thomas Graf <tgraf@...g.ch>
To:	Jesse Gross <jesse@...ira.com>
Cc:	Pravin Shelar <pshelar@...ira.com>, netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v3 net-next 5/8] geneve: Add support to collect tunnel
 metadata.

On 08/25/15 at 09:50am, Jesse Gross wrote:
> On Mon, Aug 24, 2015 at 7:15 PM, Pravin Shelar <pshelar@...ira.com> wrote:
> > Moving this device means moving all tunnels backed by this device
> > rather than specific tunnel device. Thats why it does not look right
> > to move such device.
> 
> I agree it seems weird in general. There were two things that made me wonder:
>  * It doesn't appear that VXLAN or GRE do this.
>  * The use case for moving a single tunnel to a different namespace is
> to have the device and socket live in different places. I guess
> conceptually this could apply to collect_md devices as well. (Maybe to
> have harder isolation between inside and outside the tunnel?)
> 
> I'm not really sure what the best answer is but at least we should be
> consistent across tunnel types.

I agree with Jesse that consistent behaviour is desirable. If needed,
let's change it for all encap types.
--
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