[RFT/RFC 5/5] ath10k: rx, don't pass frames with invalid FCS
Janusz Dziedzic
janusz.dziedzic at tieto.com
Thu Jul 10 04:45:14 PDT 2014
In case of bridged network, don't pass frames with
invalid FCS to the upper layer.
TODO: pass all frames in standalone monitor mode.
Signed-off-by: Janusz Dziedzic <janusz.dziedzi at tieto.com>
---
drivers/net/wireless/ath/ath10k/htt_rx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c
index 702653e..efcee32 100644
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -1173,8 +1173,7 @@ static bool ath10k_htt_rx_amsdu_allowed(struct ath10k_htt *htt,
if (status != HTT_RX_IND_MPDU_STATUS_OK &&
status != HTT_RX_IND_MPDU_STATUS_TKIP_MIC_ERR &&
- status != HTT_RX_IND_MPDU_STATUS_ERR_INV_PEER &&
- !htt->ar->monitor_started) {
+ status != HTT_RX_IND_MPDU_STATUS_ERR_INV_PEER) {
ath10k_dbg(ATH10K_DBG_HTT,
"htt rx ignoring frame w/ status %d\n",
status);
--
1.7.9.5
More information about the ath10k
mailing list