From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2][next] wifi: wil6210: Annotate a couple of structs with __counted_by()
Date: Wed, 27 Mar 2024 12:39:54 -0600 [thread overview]
Message-ID: <4e1261a7-25a9-4193-a9e9-9bc137893f08@embeddedor.com> (raw)
In-Reply-To: <5a6bdbc6-b37e-4c6b-9bff-470fd560663b@embeddedor.com>
>>> #define WMI_MAX_PNO_SSID_NUM (16)
>>> @@ -3320,7 +3320,7 @@ struct wmi_set_link_monitor_cmd {
>>> u8 rssi_hyst;
>>> u8 reserved[12];
>>> u8 rssi_thresholds_list_size;
>>> - s8 rssi_thresholds_list[];
>>> + s8 rssi_thresholds_list[] __counted_by(rssi_thresholds_list_size);
>>> } __packed;
>>
>> this looks ok to me, although I think there is another issue associated with
>> this, namely the way the code populates the rssi_thresholds_list is by
>> defining a separate anonymous struct:
>> struct {
>> struct wmi_set_link_monitor_cmd cmd;
>> s8 rssi_thold;
>> } __packed cmd = {
>> .cmd = {
>> .rssi_hyst = rssi_hyst,
>> .rssi_thresholds_list_size = 1,
>> },
>> .rssi_thold = rssi_thold,
>> };
>>
>> I would expect gcc and clang to both complain about that s8 rssi_thold comes
>> after a flexible array (even though its purpose is to be the value of
>> rssi_thresholds_list[0])
>>
I will merge these two patches together:
https://lore.kernel.org/linux-hardening/ZgODZOB4fOBvKl7R@neat/
https://lore.kernel.org/linux-hardening/ZgOEoCWguq3n1OqQ@neat/
and send these changes together with the DEFINE_FLEX() transformation
in drivers/net/wireless/ath/wil6210/cfg80211.c
diff --git a/drivers/net/wireless/ath/wil6210/wmi.h b/drivers/net/wireless/ath/wil6210/wmi.h
index 71bf2ae27a98..38f64524019e 100644
--- a/drivers/net/wireless/ath/wil6210/wmi.h
+++ b/drivers/net/wireless/ath/wil6210/wmi.h
@@ -474,7 +474,7 @@ struct wmi_start_scan_cmd {
struct {
u8 channel;
u8 reserved;
- } channel_list[];
+ } channel_list[] __counted_by(num_channels);
} __packed;
Thanks
--
Gustavo
next prev parent reply other threads:[~2024-03-27 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 17:43 Gustavo A. R. Silva
2024-03-27 18:26 ` Jeff Johnson
2024-03-27 18:34 ` Gustavo A. R. Silva
2024-03-27 18:39 ` Gustavo A. R. Silva [this message]
2024-03-27 18:53 ` 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=4e1261a7-25a9-4193-a9e9-9bc137893f08@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@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®