qcacld-3.0: WAR to handle invalid flow_idx from HW

Currently if the pkt tlvs indicate flow_invalid=0,
there is no sanity done on the SW flow table entry
retrieved using the flow_idx from pkt tlvs.

In case of HW incorrectly sending a invalid flow_idx,
within the range of allowed flow_idx, and flow_invalid=0,
there will be an attempt to aggregate an invalid flow.
This can also trigger a RX ring id mismatch.

In order to mitigate the above issue, verify if the
SW flow table has been populated, before attempting
FISA aggregation.

Change-Id: Idb445c0c5b249d747dbce61f31513ba4a75c26b7
CRs-Fixed: 3412721

components/dp/core/src/wlan_dp_fisa_rx.c

@@ -1098,6 +1098,11 @@ dp_fisa_rx_get_sw_ft_entry(struct dp_rx_fst *fisa_hdl, qdf_nbuf_t nbuf,
 	}
 
 	sw_ft_entry = &sw_ft_base[flow_idx];
+	if (!sw_ft_entry->is_populated) {
+		dp_info("Pkt rx for non configured flow idx 0x%x", flow_idx);
+		DP_STATS_INC(fisa_hdl, invalid_flow_index, 1);
+		return NULL;
+	}
 
 	if (!fisa_hdl->flow_deletion_supported) {
 		sw_ft_entry->vdev = vdev;