Re: [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Joe Stringer
On 13 July 2017 at 15:38, Greg Rose wrote: > On 07/13/2017 11:03 AM, Joe Stringer wrote: >> >> On 13 July 2017 at 11:01, Greg Rose wrote: >>> >>> On 07/13/2017 10:46 AM, Joe Stringer wrote: On 13 July 2017 at 09:25, Greg Rose wrote: > > > When there is an established c

Re: [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Greg Rose
On 07/13/2017 11:03 AM, Joe Stringer wrote: On 13 July 2017 at 11:01, Greg Rose wrote: On 07/13/2017 10:46 AM, Joe Stringer wrote: On 13 July 2017 at 09:25, Greg Rose wrote: When there is an established connection in direction A->B, it is possible to receive a packet on port B which then e

Re: [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Joe Stringer
On 13 July 2017 at 11:01, Greg Rose wrote: > On 07/13/2017 10:46 AM, Joe Stringer wrote: >> >> On 13 July 2017 at 09:25, Greg Rose wrote: >>> >>> When there is an established connection in direction A->B, it is >>> possible to receive a packet on port B which then executes >>> ct(commit,force) wi

Re: [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Greg Rose
On 07/13/2017 10:46 AM, Joe Stringer wrote: On 13 July 2017 at 09:25, Greg Rose wrote: When there is an established connection in direction A->B, it is possible to receive a packet on port B which then executes ct(commit,force) without first performing ct() - ie, a lookup. In this case, we woul

Re: [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Joe Stringer
On 13 July 2017 at 09:25, Greg Rose wrote: > When there is an established connection in direction A->B, it is > possible to receive a packet on port B which then executes > ct(commit,force) without first performing ct() - ie, a lookup. > In this case, we would expect that this packet can delete th

Re: [ovs-dev] [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Greg Rose
On 07/13/2017 10:08 AM, Darrell Ball wrote: On 7/13/17, 9:25 AM, "ovs-dev-boun...@openvswitch.org on behalf of Greg Rose" wrote: When there is an established connection in direction A->B, it is possible to receive a packet on port B which then executes ct(commit,force) without

Re: [ovs-dev] [PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Darrell Ball
On 7/13/17, 9:25 AM, "ovs-dev-boun...@openvswitch.org on behalf of Greg Rose" wrote: When there is an established connection in direction A->B, it is possible to receive a packet on port B which then executes ct(commit,force) without first performing ct() - ie, a lookup. In thi

[PATCH] datapath: Fix for force/commit action failures

2017-07-13 Thread Greg Rose
When there is an established connection in direction A->B, it is possible to receive a packet on port B which then executes ct(commit,force) without first performing ct() - ie, a lookup. In this case, we would expect that this packet can delete the existing entry so that we can commit a connection