linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
	Support Opensource <Support.Opensource@diasemi.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: da9063: Replace zero-length array with flexible-array member
Date: Wed, 12 Feb 2020 08:29:06 -0600	[thread overview]
Message-ID: <575985a9-cc82-1eae-6651-30a603f494d7@embeddedor.com> (raw)
In-Reply-To: <AM6PR10MB226386E325F5EEA41A1C47BA801B0@AM6PR10MB2263.EURPRD10.PROD.OUTLOOK.COM>



On 2/12/20 05:14, Adam Thomson wrote:
> On 11 February 2020 23:47, Gustavo A. R. Silva wrote:
> 
>> 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>
>> ---
>>  drivers/regulator/da9063-regulator.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/regulator/da9063-regulator.c b/drivers/regulator/da9063-
>> regulator.c
>> index 2b0c7a85306a..368f8ad2a9f9 100644
>> --- a/drivers/regulator/da9063-regulator.c
>> +++ b/drivers/regulator/da9063-regulator.c
>> @@ -119,7 +119,7 @@ struct da9063_regulator {
>>  struct da9063_regulators {
>>  	unsigned				n_regulators;
>>  	/* Array size to be defined during init. Keep at end. */
>> -	struct da9063_regulator			regulator[0];
>> +	struct da9063_regulator			regulator[];
> 
> Same comment as for da9062. The probe uses malloc and does not statically
> initialise for this struct so this will break the probe.
> 

Dynamic memory allocations won't be affected by this change:

"Flexible array members have incomplete type, and so the sizeof operator
may not be applied. As a quirk of the original implementation of
zero-length arrays, sizeof evaluates to zero."[1]

[1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html

Thanks
--
Gustavo

  reply	other threads:[~2020-02-12 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 23:47 [PATCH] regulator: da9063: Replace zero-length array with flexible-array member Gustavo A. R. Silva
2020-02-12 11:14 ` Adam Thomson
2020-02-12 14:29   ` Gustavo A. R. Silva [this message]
2020-02-12 14:56     ` Adam Thomson

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=575985a9-cc82-1eae-6651-30a603f494d7@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).