From: Michal Kazior <michal.kazior@tieto.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 7/7] ath10k: strip protected flag
Date: Tue, 30 Apr 2013 10:07:15 +0200 [thread overview]
Message-ID: <517F7BB3.6050200@tieto.com> (raw)
In-Reply-To: <87mwsglaao.fsf@kamboji.qca.qualcomm.com>
On 30/04/13 09:58, Kalle Valo wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> We already do decryption and all crypto
>> verification in HW. mac80211 tries to verify CCMP
>> for fragmented rx and fails without this patch.
>>
>> This fixes fragmented rx on CCMP networks.
>>
>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>
> [...]
>
>> - if (info->encrypt_type != HTT_RX_MPDU_ENCRYPT_NONE)
>> + if (info->encrypt_type != HTT_RX_MPDU_ENCRYPT_NONE) {
>> status->flag |= RX_FLAG_DECRYPTED | RX_FLAG_IV_STRIPPED |
>> RX_FLAG_MMIC_STRIPPED;
>> + hdr->frame_control = __cpu_to_le16(
>> + __le16_to_cpu(hdr->frame_control) &
>> + ~IEEE80211_FCTL_PROTECTED);
>> + }
>
> This looks ugly. Is this a bug in mac80211 which we just workaround in
> ath10k? Isn't there any other way to fix this? At least this deserves a
> big comment in the code to explain why we are doing this.
>
> I'll apply this anyway, but we need to discuss more about this.
I'm not quite sure whether this is an issue in mac80211 or we should be
actually stripping the protected flag. b43 driver seems to strip the
flag as well.
mac80211 seems to want to do some extra checks for CCMP in fragmented rx
data path. Perhaps it shouldn't?
-- Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2013-04-30 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 8:37 [ath9k-devel] [PATCH 0/7] ath10k: htt rx fixes Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 1/7] ath10k: zero htt_rx_info struct in frag rx handler Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 2/7] ath10k: do not pop more than one frame " Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 3/7] ath10k: add safety check after popping a frame in frag rx Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 4/7] ath10k: move ath10k_htt_rx_free_msdu_chain() Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 5/7] ath10k: drop all msdus in case of htt rx failure Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 6/7] ath10k: fix tkip fragment rx Michal Kazior
2013-04-26 8:37 ` [ath9k-devel] [PATCH 7/7] ath10k: strip protected flag Michal Kazior
2013-04-30 7:58 ` Kalle Valo
2013-04-30 8:07 ` Michal Kazior [this message]
2013-04-30 8:20 ` Kalle Valo
2013-04-30 8:01 ` [ath9k-devel] [PATCH 0/7] ath10k: htt rx fixes Kalle Valo
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=517F7BB3.6050200@tieto.com \
--to=michal.kazior@tieto.com \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.