netdev - Re: [ovs-dev] [PATCH] Change in openvswitch kernel module to support MPLS label depth of 3 in ingress direction.

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: <20191020190706.GC25323@ovn.org>
Date:   Sun, 20 Oct 2019 12:07:06 -0700
From:   Ben Pfaff <blp@....org>
To:     Martin Varghese <martinvarghesenokia@...il.com>
Cc:     dev@...nvswitch.org, netdev@...r.kernel.org, pshelar@....org,
        Martin Varghese <martin.varghese@...ia.com>
Subject: Re: [ovs-dev] [PATCH] Change in openvswitch kernel module to support
 MPLS label depth of 3 in ingress direction.

On Sun, Oct 20, 2019 at 07:55:32PM +0530, Martin Varghese wrote:
> From: Martin Varghese <martin.varghese@...ia.com>
> 
> The openvswitch kernel module was supporting a MPLS label depth of 1
> in the ingress direction though the userspace OVS supports a max depth
> of 3 labels. This change enables openvswitch module to support a max
> depth of 3 labels in the ingress.
> 
> Signed-off-by: Martin Varghese <martin.varghese@...ia.com>

Thanks for the patch!

Usually, for kernel module changes, the workflow is to submit the change
upstream to the Linux kernel first ("upstream first").  Then, afterward,
we backport the upstream changes into the OVS repository.

I see that you have CCed this to the Linux kernel networking list
(netdev) but the patch itself is against the OVS repo.  Probably, if you
want to get reviews from netdev, you should instead post a patch against
the net-next repository.

Thanks again for working to improve Open vSwitch.