commit f1e7b2da6553157d0ea3e24c45005387ce71cda6
Author: Anand H. Krishnan <email address hidden>
Date: Tue Mar 10 17:28:26 2015 +0530
Validate vif to device and device to vif linkage before using vif
Once rps is done, the handler tries to extract vif from the control
block. From that vif we try to get the dev and the rx_handler_data
(which should be equal to the vif). From whatever information that
was present in the trace, it was confirmed that rx_handler_data was
null. There could be a case where agent restarts and is in the process
of soft resetting the vrouter when this condition can happen. Since
we do not have dump, for now we will check the linkages between vif
and device (<=>) before proceeding with packet processing.
Reviewed: https:/ /review. opencontrail. org/8211 github. org/Juniper/ contrail- vrouter/ commit/ f1e7b2da6553157 d0ea3e24c450053 87ce71cda6
Committed: http://
Submitter: Zuul
Branch: R2.1
commit f1e7b2da6553157 d0ea3e24c450053 87ce71cda6
Author: Anand H. Krishnan <email address hidden>
Date: Tue Mar 10 17:28:26 2015 +0530
Validate vif to device and device to vif linkage before using vif
Once rps is done, the handler tries to extract vif from the control
block. From that vif we try to get the dev and the rx_handler_data
(which should be equal to the vif). From whatever information that
was present in the trace, it was confirmed that rx_handler_data was
null. There could be a case where agent restarts and is in the process
of soft resetting the vrouter when this condition can happen. Since
we do not have dump, for now we will check the linkages between vif
and device (<=>) before proceeding with packet processing.
Closes Bug: #1430279
Change-Id: I98066588c3c0d9 5f1327d505495f2 058d9616a4d