From: Govindaraj Saminathan <gsamin@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH] mac80211: fix low throughput due to invalid addba extension
Date: Tue, 06 Apr 2021 23:59:46 +0530 [thread overview]
Message-ID: <68a9d6b4eb7b77295f538f4aec3d8f84@codeaurora.org> (raw)
In-Reply-To: <631e58cbfc146db2a6ca70ffc8b90648@codeaurora.org>
On 2021-03-16 23:15, Govindaraj Saminathan wrote:
> On 2021-03-16 21:21, Johannes Berg wrote:
>> On Tue, 2021-03-16 at 21:17 +0530, Govindaraj wrote:
>>> Addba request action frame received with the extension element from
>>> certain 11ac stations,
>>>
>>
>> Please indicate which so we have a record of who's shipping broken
>> junk.
The below log i taken with pixel3 client device
>>
>>> but the cmd id and length not matching to addba
>>> extension and it failing in element parsing.
>>
>>> Due to this, addba request
>>> not acknowledged and aggregation not started which is causing low
>>> throughput. Hence validating the cmd id before processing addba
>>> extension.
>>
>>> ies_len = len - offsetof(struct ieee80211_mgmt,
>>> u.action.u.addba_req.variable);
>>> - if (ies_len) {
>>> + if (ies_len &&
>>> + mgmt->u.action.u.addba_req.variable[0] == WLAN_EID_ADDBA_EXT) {
>>> ieee802_11_parse_elems(mgmt->u.action.u.addba_req.variable,
>>> ies_len, true, &elems, mgmt->bssid,
>>> NULL);
>>> if (elems.parse_error)
>>
>> So we get into parse_error without this?
> yes, we getting parse error.
>>
>> What are they putting there instead?
> first 9 bytes are addba request action frame and remaining 7 bytes
> extension causing for parse error.
> 03 00 01 02 10 00 00 e0 0a cf 08 06 11a 46 09 fe
>>
>> johannes
prev parent reply other threads:[~2021-04-06 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 15:47 [PATCH] mac80211: fix low throughput due to invalid addba extension Govindaraj
2021-03-16 15:51 ` Johannes Berg
2021-03-16 17:45 ` Govindaraj Saminathan
2021-04-06 18:29 ` Govindaraj Saminathan [this message]
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=68a9d6b4eb7b77295f538f4aec3d8f84@codeaurora.org \
--to=gsamin@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).