From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>,
"Lubart, Vitaly" <vitaly.lubart@intel.com>
Subject: RE: [PATCH] mei: bus: replace zero-length array with flexible-array member
Date: Wed, 12 Feb 2020 22:19:48 +0000 [thread overview]
Message-ID: <71cd2c9eba7f4ac68de55148edb08e19@intel.com> (raw)
In-Reply-To: <20200211210822.GA31368@embeddedor>
> -----Original Message-----
> From: Gustavo A. R. Silva <gustavo@embeddedor.com>
> Sent: Tuesday, February 11, 2020 23:08
> To: Winkler, Tomas <tomas.winkler@intel.com>; Arnd Bergmann
> <arnd@arndb.de>; Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-kernel@vger.kernel.org; Gustavo A. R. Silva
> <gustavo@embeddedor.com>
> Subject: [PATCH] mei: bus: replace zero-length array with flexible-array member
>
> The current codebase makes use of the zero-length array language extension to
> the C90 standard, but the preferred mechanism to declare variable-length types
> such as these ones is a flexible array member[1][2], introduced in C99:
>
> struct foo {
> int stuff;
> struct boo array[];
> };
>
> By making use of the mechanism above, we will get a compiler warning in case
> the flexible array does not occur last in the structure, which will help us prevent
> some kind of undefined behavior bugs from being inadvertenly introduced[3] to
> the codebase from now on.
>
> This issue was found with the help of Coccinelle.
>
> [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
> [2] https://github.com/KSPP/linux/issues/21
> [3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Ack.
> ---
> drivers/misc/mei/bus-fixup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/mei/bus-fixup.c b/drivers/misc/mei/bus-fixup.c index
> 5fcac02233af..aa3648d59a8a 100644
> --- a/drivers/misc/mei/bus-fixup.c
> +++ b/drivers/misc/mei/bus-fixup.c
> @@ -107,7 +107,7 @@ struct mkhi_rule_id { struct mkhi_fwcaps {
> struct mkhi_rule_id id;
> u8 len;
> - u8 data[0];
> + u8 data[];
> } __packed;
>
> struct mkhi_fw_ver_block {
> @@ -135,7 +135,7 @@ struct mkhi_msg_hdr {
>
> struct mkhi_msg {
> struct mkhi_msg_hdr hdr;
> - u8 data[0];
> + u8 data[];
> } __packed;
>
> #define MKHI_OSVER_BUF_LEN (sizeof(struct mkhi_msg_hdr) + \
> --
> 2.25.0
prev parent reply other threads:[~2020-02-12 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 21:08 [PATCH] mei: bus: replace zero-length array with flexible-array member Gustavo A. R. Silva
2020-02-12 22:19 ` Winkler, Tomas [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=71cd2c9eba7f4ac68de55148edb08e19@intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vitaly.lubart@intel.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