[ovs-dev] [PATCH 0/8] port Jiri's 8 support patches for layer 3 encapsulated packets from net-next

[Yang, Yi Y]

Hi, Joe and Pravin

I checked " make check-kernel" against current ovs master (I don't add any change) on Ubuntu 14.04, but it failed

## ------------------------------ ##
## openvswitch 2.6.90 test suite. ##
## ------------------------------ ##

datapath-sanity

  1: datapath - ping between two ports               FAILED (system-traffic.at:13)
  2: datapath - http between two ports               FAILED (system-traffic.at:36)

I don't know what we need to prepare in order that it can be run correctly.

" make check-kmod" has the same result. Notice, I didn't add a line code, I just cloned ovs master and tried it after build.

## ------------------------------ ##
## openvswitch 2.6.90 test suite. ##
## ------------------------------ ##

datapath-sanity

  1: datapath - ping between two ports               FAILED (system-traffic.at:13)
  2: datapath - http between two ports               FAILED (system-traffic.at:36)
  3: datapath - ping between two ports on vlan       FAILED (system-traffic.at:59)

-----Original Message-----
From: Pravin Shelar [mailto:pshelar at ovn.org] 
Sent: Friday, December 16, 2016 3:30 PM
To: Joe Stringer <joe at ovn.org>
Cc: Yang, Yi Y <yi.y.yang at intel.com>; ovs dev <dev at openvswitch.org>
Subject: Re: [ovs-dev] [PATCH 0/8] port Jiri's 8 support patches for layer 3 encapsulated packets from net-next

On Thu, Dec 15, 2016 at 5:23 PM, Joe Stringer <joe at ovn.org> wrote:
> On 15 December 2016 at 05:27, Yi Yang <yi.y.yang at intel.com> wrote:
>> This patch set just ports Jiri's 8 support patches for layer 3 encapsulated packets from net-next to current ovs, this is a cornerstone for L3 tunnel port support in ovs.
>
> Please follow the directions for submitting patches:
> http://docs.openvswitch.org/en/latest/internals/contributing/submittin
> g-patches/
>
> In particular, I see a variety of complaints from the compiler with 
> this series, some of them may apply to upstream as well [I didn't get 
> as far as to check that yet], some are just warnings but we should 
> certainly fix them anyway; some are userspace compilation failures 
> with the newer headers.
>
> It would also provide further validation of the series if A) you can 
> point to a good full travis-ci run with this series; and B) if you 
> could run the kernel module testsuite to confirm things don't break. I 
> believe that Jarno had some pending patches for breakage introduced by 
> this series.
>
I agree, we need to sort out those issues upstream before merging it to out of tree kernel module.