netdev - Re: [PATCH net] vxlan: revert per-vxlan port

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:	Wed, 22 May 2013 17:39:54 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org
Subject: Re: [PATCH net] vxlan: revert per-vxlan port

On Wed, 22 May 2013 19:18:12 -0400
David Stevens <dlstevens@...ibm.com> wrote:

> David Miller <davem@...emloft.net> wrote on 05/22/2013 06:08:30 PM:
> 
> > David, please come to some kind of agreement with Stephen about what
> > we're going to do about this.
> 
> Well, I think being able to specify an alternate port for the
> default fdb entry is a useful feature in its own right. It is
> not equivalent to individual fdb entries with alternate ports
> because those require the host to know all the destinations in
> advance. It's certainly reasonable to use an alternate port for
> the default entry as well, and is not "useless" without multiple
> listen ports; it is as useful for the default port as it is for
> individual fdb entries.
> 
> I'm not sure what the benefit of reverting any working feature
> is, only to re-add it later, which I believe is what Stephen
> is proposing. I think it is useful for some configurations now,
> even if it only becomes useful for other configurations after
> multiple listen ports.
> 
> Stephen, can you explain what the benefit of reverting this is?
> 
> I think we want it long term, but I can live without it
> temporarily. I just don't see any reasoning for removing it
> temporarily in the first place. It isn't broken, or breaking
> anything else, after all.
> 
>                                                 +-DLS
> 

There are two different config things here
  1. FDB - NDA_PORT
  2. VXLAN - IFLA_VXLAN_PORT

The FDB stuff is seperate and fine, Dave did a complete job on that.
I was confused, but it's fine.

The per-vxlan device stuff is the issue. I don't think it works
as is in 3.10 because there is no real way to use it to receive.
And don't want to let it out broken. By reverting that part, we avoid
raising false expectations.

--
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