From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Maya Erez <merez@codeaurora.org>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org, wil6210@qti.qualcomm.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH][next] wil6210: Avoid the use of one-element array
Date: Wed, 22 Jul 2020 15:00:30 -0500 [thread overview]
Message-ID: <ea440f6c-577b-3733-0eb1-846d46559fb0@embeddedor.com> (raw)
In-Reply-To: <adb69bc4b83d9a03ac4e8a4556f79a72c7a6f2cc.camel@sipsolutions.net>
On 7/22/20 14:40, Johannes Berg wrote:
> On Wed, 2020-07-15 at 16:57 -0500, Gustavo A. R. Silva wrote:
>> One-element arrays are being deprecated[1]. Replace the one-element
>> array with a simple value type 'u8 reserved'[2], once this is just
>> a placeholder for alignment.
>>
>> [1] https://github.com/KSPP/linux/issues/79
>> [2] https://github.com/KSPP/linux/issues/86
>
> Umm, no, you're misinterpreting this ... This has nothing to do with
> variable length and isn't used that way. As you can see from your own
> patch, since you're not changing any users.
>
I understand that this 'reserved' field is being used merely for alignment
purposes:
drivers/net/wireless/ath/wil6210/wmi.h:
3080 /* WMI_SCHEDULING_SCHEME_EVENTID */
3081 struct wmi_scheduling_scheme_event {
3082 /* wmi_fw_status_e */
3083 u8 status;
3084 /* serial number given in command */
3085 u8 serial_num;
3086 /* wmi_sched_scheme_failure_type */
3087 u8 failure_type;
3088 /* alignment to 32b */
3089 u8 reserved[1];
3090 } __packed;
and that it's not being used as a variable-length array. The links are included
to inform the people about the reason why we are removing zero-length/one-element
arrays in the first place. The thing in this case is that it doesn't hurt to use
a simple value type instead of the one-element array form.
Thanks
--
Gustavo
next prev parent reply other threads:[~2020-07-22 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 21:57 Gustavo A. R. Silva
2020-07-22 18:27 ` Gustavo A. R. Silva
2020-07-23 6:43 ` Kalle Valo
2020-07-24 18:29 ` Gustavo A. R. Silva
2020-07-22 19:40 ` Johannes Berg
2020-07-22 20:00 ` Gustavo A. R. Silva [this message]
2020-08-14 14:47 ` Kalle Valo
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=ea440f6c-577b-3733-0eb1-846d46559fb0@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=davem@davemloft.net \
--cc=gustavoars@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=merez@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=wil6210@qti.qualcomm.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®