[ovs-discuss] Warning logs flooding: failed to flow_del (No such file or directory)

[Alex Wang]

On Tue, Jul 1, 2014 at 7:38 PM, Han Zhou <zhouhan at gmail.com> wrote:

> Hi Alex,
>
> That's cool!
> Just one more question.
> >    Due to the race condition in userspace, there is chance that two
> >    overlapping megaflows could be installed in datapath.  And this
> >    causes userspace unable to delete the less inclusive megaflow flow
> >    even after it timeout, since the flow_del logic will stop at the
> >    first match of masked flow.
>
> Does it mean if the more inclusive megaflow (say A) is deleted, then
> the less inclusive megaflow (say B) can be deleted? If so, I can have
> a workaround without updating OVS version: I can find out the more
> inclusive megaflow and manually delete flows with ovs-dpctl in order
> (A -> B), then warning logs should stop, right?


Right.  Note you should prevent the relevant traffic from installing the
'more inclusive' flow between deletions.

Thanks,
Alex Wang,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140701/a6f38b81/attachment-0002.html>