On 17 May 2017 at 06:43, Alin Serdean <[email protected]> wrote:
> When a conntrack action is applied over an IP fragment we pend the fragment > which will be consumed later. This should be transparent to the userspace. > > Report that the action was applied successfully so it does not spam > the ovs-vswitchd log. > > Signed-off-by: Alin Gabriel Serdean <[email protected]> > Thanks, applied! > --- > datapath-windows/ovsext/Actions.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/datapath-windows/ovsext/Actions.c b/datapath-windows/ovsext/ > Actions.c > index ebfb8a3..31b4514 100644 > --- a/datapath-windows/ovsext/Actions.c > +++ b/datapath-windows/ovsext/Actions.c > @@ -2032,6 +2032,11 @@ OvsDoExecuteActions(POVS_SWITCH_CONTEXT > switchContext, > if (status != NDIS_STATUS_PENDING) { > OVS_LOG_ERROR("CT Action failed"); > dropReason = L"OVS-conntrack action failed"; > + } else { > + /* We added a new pending NBL to be consumed later. > + * Report to the userspace that the action applied > + * successfully */ > + status = NDIS_STATUS_SUCCESS; > } > goto dropit; > } else if (oldNbl != ovsFwdCtx.curNbl) { > -- > 2.10.2.windows.1 > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
