vs-dev-
> boun...@openvswitch.org] On Behalf Of Sairam Venugopal
> Sent: Friday, December 8, 2017 1:26 AM
> To: aserd...@ovn.org; 'Justin Pettit' <jpet...@ovn.org>;
> d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] datapath-windows: Correct endianness for
> deleting zone
.@openvswitch.org; Alin Gabriel Serdean <aserd...@ovn.org>;
>> Sairam Venugopal <vsai...@vmware.com>
>> Subject: [ovs-dev] [PATCH] datapath-windows: Correct endianness for
>> deleting zone.
>>
>> The zone Netlink attribute is supposed to be in network-byte ord
> On Dec 7, 2017, at 2:57 PM, Sairam Venugopal wrote:
>
> Thanks for the patch. Discussed about the patch offline.
>
> This is required since we have now introduced a newer api for deleting
> 5-tuples
> and this breaks the assumption of zone-id not being in the right
Thanks for the patch. Discussed about the patch offline.
This is required since we have now introduced a newer api for deleting 5-tuples
and this breaks the assumption of zone-id not being in the right byte order.
Acked-by: Sairam Venugopal
On 12/4/17, 11:30 PM,
opal <vsai...@vmware.com>
> Subject: [ovs-dev] [PATCH] datapath-windows: Correct endianness for
> deleting zone.
>
> The zone Netlink attribute is supposed to be in network-byte order, but
the
> Windows code for deleting conntrack entries was treating it as host-byte
> order.
>
The zone Netlink attribute is supposed to be in network-byte order, but
the Windows code for deleting conntrack entries was treating it as
host-byte order.
Found by inspection.
Signed-off-by: Justin Pettit
---
datapath-windows/ovsext/Conntrack.c | 2 +-
lib/netlink-conntrack.c