All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] treewide: Replace zero-length arrays with flexible-array member
Date: Tue, 11 Feb 2020 11:35:50 -0800	[thread overview]
Message-ID: <202002111132.4A4F073CAF@keescook> (raw)
In-Reply-To: <20200211174126.GA29960@embeddedor>

On Tue, Feb 11, 2020 at 11:41:26AM -0600, 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
> unadvertenly introduced[3] to the codebase from now on.

Is there a compiler warning we can enable to avoid new 0-byte arrays
from entering the kernel source tree? I can only find "-pedantic" which
enables way too many other checks.

-- 
Kees Cook

  parent reply	other threads:[~2020-02-11 19:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 17:41 [PATCH] treewide: Replace zero-length arrays with flexible-array member Gustavo A. R. Silva
2020-02-11 18:32 ` Greg KH
2020-02-11 19:20   ` Gustavo A. R. Silva
2020-02-11 19:32     ` Kees Cook
2020-02-11 19:38       ` Greg KH
2020-02-11 19:54         ` Gustavo A. R. Silva
2020-02-11 20:12           ` Kees Cook
2020-02-11 20:30             ` Gustavo A. R. Silva
2020-02-11 19:35 ` Kees Cook [this message]
2020-02-11 20:16   ` Gustavo A. R. Silva
2020-02-12  8:00 ` Geert Uytterhoeven
2020-02-12  8:36   ` Kars de Jong
2020-02-13 11:09 ` Geert Uytterhoeven
2020-02-13 11:11   ` Ard Biesheuvel

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=202002111132.4A4F073CAF@keescook \
    --to=keescook@chromium.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.