Taken the fix from the commit d3292dd... (in ovn-controller-vtep.at)
Signed-off-by: Numan Siddique
---
tests/ovn-nbctl.at | 10 +-
tests/ovn-sbctl.at | 10 +-
2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/tests/ovn-nbctl.at b/tests/ovn-nbctl.at
index 5358f1e..ef
STT receive can accept packet on device which is not UP state.
Following patch fixes this issue by introducing another list
of devices which contains only devices in up state. This list can
be used for searching stt devices on packet receive.
Signed-off-by: Pravin B Shelar
---
datapath/linux/com
On Sun, Dec 20, 2015 at 5:48 PM, Pravin Shelar wrote:
> On Sun, Dec 20, 2015 at 10:31 AM, Jesse Gross wrote:
>> One other thing that I noticed is that the STT fragment hash table
>> commingles fragments that were addressed to different destination
>> ports. This is unlikely to matter with the cur
On Sun, Dec 20, 2015 at 10:31 AM, Jesse Gross wrote:
> On Sun, Dec 20, 2015 at 1:21 AM, Pravin B Shelar wrote:
>> Keep devices in UP state in stt-list. So that devices in UP state
>> would be searched on a packet receive in STT. This way devices in
>> DOWN state would not accept any packets.
>>
>
On Sun, Dec 20, 2015 at 9:07 AM, Jesse Gross wrote:
> On Sun, Dec 20, 2015 at 1:21 AM, Pravin B Shelar wrote:
>> The bug was reported by Joe Stringer.
>>
>> Signed-off-by: Pravin B Shelar
>
> Acked-by: Jesse Gross
Thanks. I pushed it to master and branch-2.5.
_
On Sun, Dec 20, 2015 at 12:16 PM, Joe Stringer wrote:
> On 19 December 2015 at 19:19, Pravin B Shelar wrote:
>> STT device is added to the device list at device create time. and
>> the dev socket is initialized when dev is UP. So avoid accessing
>> stt socket while searching a device.
>>
>> ---8<
On Sun, Dec 20, 2015 at 9:30 AM, Jesse Gross wrote:
> On Sat, Dec 19, 2015 at 10:19 PM, Pravin B Shelar wrote:
>> STT device is added to the device list at device create time. and
>> the dev socket is initialized when dev is UP. So avoid accessing
>> stt socket while searching a device.
>>
>> ---
On 19 December 2015 at 19:19, Pravin B Shelar wrote:
> STT device is added to the device list at device create time. and
> the dev socket is initialized when dev is UP. So avoid accessing
> stt socket while searching a device.
>
> ---8<---
> IP: [] nf_ip_hook+0xfd/0x180 [openvswitch]
> Oops:
On Sun, Dec 20, 2015 at 1:21 AM, Pravin B Shelar wrote:
> Keep devices in UP state in stt-list. So that devices in UP state
> would be searched on a packet receive in STT. This way devices in
> DOWN state would not accept any packets.
>
> Signed-off-by: Pravin B Shelar
I think this works but it
On Sun, Dec 20, 2015 at 3:57 AM, Wanlong Gao wrote:
> Backport from the upstream commit, this commit is necessary for using
> 2.3.x on RHEL with updated kernel, and absolutely more sane than the kernel
> version adjudgement:
> commit 572e54faff70760f4bfe4a7cffc9553e6743199e
Thanks, cherry
On Sat, Dec 19, 2015 at 10:19 PM, Pravin B Shelar wrote:
> STT device is added to the device list at device create time. and
> the dev socket is initialized when dev is UP. So avoid accessing
> stt socket while searching a device.
>
> ---8<---
> IP: [] nf_ip_hook+0xfd/0x180 [openvswitch]
> Oops: 0
On Sun, Dec 20, 2015 at 1:21 AM, Pravin B Shelar wrote:
> The bug was reported by Joe Stringer.
>
> Signed-off-by: Pravin B Shelar
Acked-by: Jesse Gross
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
From: Ofer Ben-Yacov
Currently the IDL does not support passive TCP connection,
i.e. when the OVSDB connects to its manager.
This patch enables IDL to use an already-open session
(the one which was previously used for retrieving the db schema).
In addition, it enables IDL to go back to "listen m
On 12/20/2015 08:12 AM, Ofer Ben-Yacov wrote:
> Hi Russel,
>
> to answer your questions:
> 1. limitation: the use case for passive mode is that I'm integrating IDL
> to L2GW project and passive mode is prerequisite. The change that will
> enable usage of the same IP and PORT (full blown server) wi
Hi Russel,
to answer your questions:
1. limitation: the use case for passive mode is that I'm integrating IDL to
L2GW project and passive mode is prerequisite. The change that will enable
usage of the same IP and PORT (full blown server) will require much more
code changes, probably to Neutron als
Backport from the upstream commit, this commit is necessary for using
2.3.x on RHEL with updated kernel, and absolutely more sane than the kernel
version adjudgement:
commit 572e54faff70760f4bfe4a7cffc9553e6743199e
Author: Flavio Leitner
Date: Fri Aug 28 21:52:36 2015 -03
On Sun, Dec 20, 2015 at 12:21 AM, Joe Stringer wrote:
> On 19 December 2015 at 19:19, Pravin B Shelar wrote:
>> STT device is added to the device list at device create time. and
>> the dev socket is initialized when dev is UP. So avoid accessing
>> stt socket while searching a device.
>
> Is it u
On Sun, Dec 20, 2015 at 12:13 AM, Joe Stringer wrote:
> On 19 December 2015 at 19:19, Pravin B Shelar wrote:
>> STT device is added to the device list at device create time. and
>> the dev socket is initialized when dev is UP. So avoid accessing
>> stt socket while searching a device.
>>
>> ---8<
On 19 December 2015 at 19:19, Pravin B Shelar wrote:
> STT device is added to the device list at device create time. and
> the dev socket is initialized when dev is UP. So avoid accessing
> stt socket while searching a device.
Is it usual to accept packets while the device is down? Shouldn't we
j
On 19 December 2015 at 19:19, Pravin B Shelar wrote:
> STT device is added to the device list at device create time. and
> the dev socket is initialized when dev is UP. So avoid accessing
> stt socket while searching a device.
>
> ---8<---
> IP: [] nf_ip_hook+0xfd/0x180 [openvswitch]
> Oops:
20 matches
Mail list logo
