From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH for-5.18 v2] ath9k: Fix usage of driver-private space in tx_info
Date: Mon, 04 Apr 2022 22:45:46 +0200 [thread overview]
Message-ID: <877d84efwl.fsf@toke.dk> (raw)
In-Reply-To: <20220404222655.7276fb9d@gmx.net>
Peter Seiderer <ps.report@gmx.net> writes:
> Hello Toke,
>
> On Mon, 4 Apr 2022 20:11:51 +0200, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> From: Toke Høiland-Jørgensen <toke@redhat.com>
>>
>> The ieee80211_tx_info_clear_status() helper also clears the rate counts and
>> the driver-private part of struct ieee80211_tx_info, so using it breaks
>> quite a few other things. So back out of using it, and instead define a
>> ath-internal helper that only clears the area between the
>> status_driver_data and the rates info. Combined with moving the
>> ath_frame_info struct to status_driver_data, this avoids clearing anything
>> we shouldn't be, and so we can keep the existing code for handling the rate
>> information.
>>
>> While fixing this I also noticed that the setting of
>> tx_info->status.rates[tx_rateindex].count on hardware underrun errors was
>> always immediately overridden by the normal setting of the same fields, so
>> rearrange the code so that the underrun detection actually takes effect.
>>
>> The new helper could be generalised to a 'memset_between()' helper, but
>> leave it as a driver-internal helper for now since this needs to go to
>> stable.
>>
>> Cc: stable@vger.kernel.org
>> Reported-by: Peter Seiderer <ps.report@gmx.net>
>> Fixes: 037250f0a45c ("ath9k: Properly clear TX status area before reporting to mac80211")
>> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
>> ---
>> drivers/net/wireless/ath/ath9k/xmit.c | 30 ++++++++++++++++++---------
>> 1 file changed, 20 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c
>> index cbcf96ac303e..db83cc4ba810 100644
>> --- a/drivers/net/wireless/ath/ath9k/xmit.c
>> +++ b/drivers/net/wireless/ath/ath9k/xmit.c
>> @@ -141,8 +141,8 @@ static struct ath_frame_info *get_frame_info(struct sk_buff *skb)
>> {
>> struct ieee80211_tx_info *tx_info = IEEE80211_SKB_CB(skb);
>> BUILD_BUG_ON(sizeof(struct ath_frame_info) >
>> - sizeof(tx_info->rate_driver_data));
>> - return (struct ath_frame_info *) &tx_info->rate_driver_data[0];
>> + sizeof(tx_info->status.status_driver_data));
>> + return (struct ath_frame_info *) &tx_info->status.status_driver_data[0];
>> }
>
> Would be too easy if all locations would use get_frame_info()..., at least one location
> in drivers/net/wireless/ath/ath9k/main.c uses direct access:
>
> 841 txinfo = IEEE80211_SKB_CB(bf->bf_mpdu);
> 842 fi = (struct ath_frame_info *)&txinfo->rate_driver_data[0];
> 843 if (fi->keyix == keyix)
> 844 return true;
Ah, bugger; nice find! I'll fix that up as well, but I do believe it's
the only one.
-Toke
prev parent reply other threads:[~2022-04-04 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 18:11 [PATCH for-5.18 v2] ath9k: Fix usage of driver-private space in tx_info Toke Høiland-Jørgensen
2022-04-04 20:26 ` Peter Seiderer
2022-04-04 20:45 ` Toke Høiland-Jørgensen [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=877d84efwl.fsf@toke.dk \
--to=toke@toke.dk \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ps.report@gmx.net \
--cc=stable@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).