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

2017-07-14 Thread Greg Rose
On 07/14/2017 11:42 AM, Joe Stringer wrote: On 14 July 2017 at 09:10, 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,

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

2017-07-14 Thread Joe Stringer
On 14 July 2017 at 09:10, 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: [PATCH net] openvswitch: Fix for force/commit action failures

2017-07-14 Thread Joe Stringer
On 14 July 2017 at 09:10, 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

[PATCH net] openvswitch: Fix for force/commit action failures

2017-07-14 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