netdev - Re: [PATCH net] openvswitch: Fix egress tunnel info.

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, 6 Oct 2015 14:16:02 -0700
From:	Pravin Shelar <pshelar@...ira.com>
To:	Jiri Benc <jbenc@...hat.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net] openvswitch: Fix egress tunnel info.

On Tue, Oct 6, 2015 at 12:32 PM, Jiri Benc <jbenc@...hat.com> wrote:
> On Tue, 6 Oct 2015 12:21:24 -0700, Pravin Shelar wrote:
>> It should report the flag when device parameters are requested by
>> userspace if there is support for lwtunnel. So check for the flag
>> should be good enough test for lwtunnel support. Why is that not
>> reliable check?
>
> Which device? You'll need to create one before querying it. Which won't
> work so nicely for older kernels. Basically, what the user space would
> have to do is trying to create a vxlan interface and then deleting it
> and going the tunnel vport way. It can be quite confusing, I'm afraid.
>

When OVS needs to add a vxlan tunnel device, OVS can create the vxlan
device and check the parameters for the flag. If the flag does not
exist then fallback to vport-create. This only needs to be done for
very first tunnel device. Thats how most of features are supported in
OVS.
Sorry, but I do not see where is the confusion.
--
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