Issue:
------
pkt is already parsed and enqueue to the right flow table
partition, where while parsing it also calculate source
and destination ports based on fat flow configuration from
interface, using the flow key it identifies flow table
partition
But now in processing flow module do parsing of pkt again
where fat flow config is available on interface (which was
not available earlier) where it will end up changing the
port to zero and can cause a different table hash than the
flow event queue processing resulting in in-consistent
state and crash.
Reviewed: https:/ /review. opencontrail. org/23868 github. org/Juniper/ contrail- controller/ commit/ d32524d9e07040c f60aa5f81e44a5a 56fcf6596c
Committed: http://
Submitter: Zuul
Branch: master
commit d32524d9e07040c f60aa5f81e44a5a 56fcf6596c
Author: Prabhjot Singh Sethi <email address hidden>
Date: Fri Sep 2 09:05:57 2016 -0700
Fix inconsistent state in flow handling from pkt
Issue:
------
pkt is already parsed and enqueue to the right flow table
partition, where while parsing it also calculate source
and destination ports based on fat flow configuration from
interface, using the flow key it identifies flow table
partition
But now in processing flow module do parsing of pkt again
where fat flow config is available on interface (which was
not available earlier) where it will end up changing the
port to zero and can cause a different table hash than the
flow event queue processing resulting in in-consistent
state and crash.
Fix:
----
remove code causing re-parsing of pkt.
Change-Id: I36aacf35d83c06 e3329531d20b8dd 6ad6a828f19
Closes-Bug: 1619433