From: Aaradhana Sahu <quic_aarasahu@quicinc.com>
To: <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>,
Sathishkumar Muruganandam <quic_murugana@quicinc.com>,
Aaradhana Sahu <quic_aarasahu@quicinc.com>
Subject: [PATCH 1/3] wifi: mac80211: Fix tkip encrypted packet transmission path
Date: Mon, 5 Jun 2023 17:47:20 +0530 [thread overview]
Message-ID: <20230605121722.20797-2-quic_aarasahu@quicinc.com> (raw)
In-Reply-To: <20230605121722.20797-1-quic_aarasahu@quicinc.com>
From: Sathishkumar Muruganandam <quic_murugana@quicinc.com>
Currently, TKIP encrypted packets are transmitting through fast path
and fast_tx, fast_rx is not assigned in case of TKIP cipher so
packet is dropped during ping.
Fix this issue by sending TKIP encrypted packets through normal path
Signed-off-by: Sathishkumar Muruganandam <quic_murugana@quicinc.com>
Signed-off-by: Aaradhana Sahu <quic_aarasahu@quicinc.com>
---
net/mac80211/tx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
index dfe6b9c9b29e..2d9af96783f1 100644
--- a/net/mac80211/tx.c
+++ b/net/mac80211/tx.c
@@ -4681,8 +4681,7 @@ netdev_tx_t ieee80211_subif_start_xmit_8023(struct sk_buff *skb,
if (!key)
key = rcu_dereference(sdata->default_unicast_key);
- if (key && (!(key->flags & KEY_FLAG_UPLOADED_TO_HARDWARE) ||
- key->conf.cipher == WLAN_CIPHER_SUITE_TKIP))
+ if (key && (!(key->flags & KEY_FLAG_UPLOADED_TO_HARDWARE)))
goto skip_offload;
sk_pacing_shift_update(skb->sk, sdata->local->hw.tx_sk_pacing_shift);
--
2.17.1
next prev parent reply other threads:[~2023-06-05 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 12:17 [PATCH 0/3] Enable TKIP when using encapsulation offloading Aaradhana Sahu
2023-06-05 12:17 ` Aaradhana Sahu [this message]
2023-06-05 12:17 ` [PATCH 2/3] wifi: ath11k: Fix tkip encryption traffic failure Aaradhana Sahu
2023-06-05 12:17 ` [PATCH 3/3] wifi: ath11k: add 802.3 undecap support to fix TKIP MIC error reporting Aaradhana Sahu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230605121722.20797-2-quic_aarasahu@quicinc.com \
--to=quic_aarasahu@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_murugana@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).