From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: skb_cb corruption in ath10k
Date: Thu, 24 Dec 2020 09:08:13 -0800 [thread overview]
Message-ID: <c79bb1d2-3571-4f3f-12a8-bce6701a7241@candelatech.com> (raw)
In-Reply-To: <86170a90-da2f-3227-d7e5-fe9486156705@candelatech.com>
On 12/21/20 3:55 PM, Ben Greear wrote:
> Hello,
>
> I'm trying to figure out what changed in the last few kernels that is making:
>
> struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
> if (info->control.flags & IEEE80211_TX_CTRL_RATE_INJECT)
> /* why is code here all of a sudden */
>
> in data frames in ath10k,
> when, to the best of my knowledge, nothing should be setting that up in the stack.
>
> My guess is that something is stepping on the cb field somewhere in ath10k,
> but I am not sure where that might be at this point.
>
> And it also appears mac80211 or maybe supplicant is setting the rate-inject flag on some mgt frames,
> but I think that is a separate concern at this point.
>
> If anyone has any ideas of likely points, please let me know.
This issue was me being confused about how the ath10k skb_cb sits in
the same memory as the iee skb_cb. I just needed to reorder the
ath10k-skb-cb struct a bit to not clobber the control.flags area.
I also see no reason not to natually pack that stuct so that the
pointers are 8-byte aligned. Any idea why it is force-packed
currently instead of using proper padding?
Thanks,
Ben
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2020-12-24 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 23:55 skb_cb corruption in ath10k Ben Greear
2020-12-24 17:08 ` Ben Greear [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=c79bb1d2-3571-4f3f-12a8-bce6701a7241@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--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