From: Johannes Berg <johannes@sipsolutions.net>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Aditya Kumar Singh <quic_adisi@quicinc.com>
Subject: Re: [PATCH][next] wifi: mac80211: ieee80211_i: Avoid dozens of -Wflex-array-member-not-at-end warnings
Date: Fri, 25 Oct 2024 22:48:30 +0200 [thread overview]
Message-ID: <192eb05afffd37bd13ff9bc1fc9b044b347b5dc4.camel@sipsolutions.net> (raw)
In-Reply-To: <8152a551-1813-4d44-a203-45d30f2ac671@embeddedor.com>
On Fri, 2024-10-25 at 14:36 -0600, Gustavo A. R. Silva wrote:
> > >
> > > Yeah, I was actually going to mention this commit, as it's the one that introduced
> > > that `bool radar_detected` to the flex struct. However, it wasn't obvious to me
> > > how `struct ieee80211_chanctx_conf conf` could overwrite `radar_detected` as I didn't
> > > see `conf->drv_priv` being accessed through `struct struct ieee80211_chanctx_conf`.
> >
> > You have to look at the drivers, see hwsim_clear_chanctx_magic() for
> > example; I wonder why hwsim_check_chanctx_magic() never caught this.
>
> Sorry, I actually meant through `struct ieee80211_chanctx`. Something like:
>
> struct ieee80211_chanctx *foo;
> ...
>
> foo->conf.drv_priv[i] = something;
>
> or
>
> struct bar *ptr = (void *)foo->conf->drv_priv;
> then write something into *ptr...
>
> In the above cases the code will indeed overwrite `radar_detected`.
Right, that's what it does though, no? Except it doesn't have, in the
driver, "foo->conf." because mac80211 only gives it a pointer to conf,
so it's only "conf->drv_priv" (and it's the "struct bar" example.)
So yeah, pretty sure it will overwrite that, and I do wonder why it
wasn't caught. I guess no radar detection tests with MLO yet.
johannes
next prev parent reply other threads:[~2024-10-25 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 20:10 Gustavo A. R. Silva
2024-10-25 20:14 ` Johannes Berg
2024-10-25 20:22 ` Gustavo A. R. Silva
2024-10-25 20:25 ` Johannes Berg
2024-10-25 20:36 ` Gustavo A. R. Silva
2024-10-25 20:48 ` Johannes Berg [this message]
2024-10-25 21:10 ` Gustavo A. R. Silva
2024-10-25 21:16 ` Johannes Berg
2024-10-25 21:38 ` Gustavo A. R. Silva
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=192eb05afffd37bd13ff9bc1fc9b044b347b5dc4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@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
all inboxes | Powered by JetHome®