mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: i2c-multi-instantiate: Replace zero-length array with flexible-array member
Date: Thu, 27 Feb 2020 13:40:17 -0600	[thread overview]
Message-ID: <50d9bf1b-e8a4-4ca8-ed40-fbbcd297218d@embeddedor.com> (raw)
In-Reply-To: <582c09ec-a6aa-72fe-7566-7fb70c156c4d@redhat.com>



On 2/27/20 13:01, Hans de Goede wrote:
> Hi,
> 
> 
> On 2/27/20 8:03 PM, Gustavo A. R. Silva wrote:
>> Hi all,
>>
>> Friendly ping: who can take this?
> 
> FWIW, the patch looks good to me:
> 
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> 

Thanks, Hans.
--
Gustavo

> Regards,
> 
> Hans
> 
> 
> 
>> On 2/12/20 18:55, 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
>>> inadvertently introduced[3] to the codebase from now on.
>>>
>>> Also, notice that, 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]
>>>
>>> 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/platform/x86/i2c-multi-instantiate.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/platform/x86/i2c-multi-instantiate.c b/drivers/platform/x86/i2c-multi-instantiate.c
>>> index ffb8d5d1eb5f..6acc8457866e 100644
>>> --- a/drivers/platform/x86/i2c-multi-instantiate.c
>>> +++ b/drivers/platform/x86/i2c-multi-instantiate.c
>>> @@ -28,7 +28,7 @@ struct i2c_inst_data {
>>>     struct i2c_multi_inst_data {
>>>       int num_clients;
>>> -    struct i2c_client *clients[0];
>>> +    struct i2c_client *clients[];
>>>   };
>>>     static int i2c_multi_inst_count(struct acpi_resource *ares, void *data)
>>>
>>
> 

      reply	other threads:[~2020-02-27 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  0:55 Gustavo A. R. Silva
2020-02-27 19:03 ` Gustavo A. R. Silva
2020-02-27 19:01   ` Hans de Goede
2020-02-27 19:40     ` Gustavo A. R. Silva [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=50d9bf1b-e8a4-4ca8-ed40-fbbcd297218d@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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

Powered by JetHome