[ovs-dev] Possible regression in "datapath: Mega flow implementation"
jpettit at nicira.com
Thu Jun 27 06:17:50 UTC 2013
I was noticing some similar IPv6 issues earlier this evening. I'm planning to dig into it more in the morning, so I may have additional information then. Simon, if you wanted to see the flow that triggered this, you could try starting OVS with the "dpif" logging set at "dbg". This will show the flow put and dumps, and may provide some useful information, since the output below looks strange with the 0 UDP ports. If you don't have a chance, I'll do it as part of my debugging tomorrow.
On Jun 26, 2013, at 11:06 PM, Simon Horman <horms at verge.net.au> wrote:
> Hi Jesse, Hi Andy,
> I have observed what seems to be a regression added
> by "datapath: Mega flow implementation" which is still present in
> master as of 7431e17196fdb1c3189d67e3aeed4adeab4cf479
> ("ofproto-dpif: Always un-wildcard 'dl_type'.").
> The problem that I am observing is that in some cases
> ovs-vswitchd asks the (kernel) datapath to remove facets
> which the latter claims do not exist.
> The case where I see this is the facet set up as a result
> of IPv6 router solicitation requests sent when the link
> to the bridge is brought up as part of system initialisation -
> my test runs in a (usually short-lived) KVM instance.
> A sample log message is as follows:
> 2013-06-27T05:13:13Z|00039|dpif|WARN|system at ovs-system: failed to flow_del (No such file or directory) in_port(3),skb_mark(0),eth(src=4a:08:11:f1:13:f0,dst=33:33:00:00:00:fb),eth_type(0x86dd),ipv6(src=fe80::14e9:14e9:fef1:13f0,dst=ff02::fb,label=0,proto=17,tclass=0,hlimit=255,frag=no),udp(src=0,dst=0)
> dev mailing list
> dev at openvswitch.org
More information about the dev