linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Jann Horn <jannh@google.com>
Cc: Stefan Agner <stefan@agner.ch>, Lucas Stach <dev@lynxeye.de>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-mtd@lists.infradead.org, linux-tegra@vger.kernel.org,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] mtd: rawnand: Replace one-element array with flexible-array member
Date: Wed, 30 Sep 2020 16:36:34 -0500	[thread overview]
Message-ID: <20200930213634.GA12855@embeddedor> (raw)
In-Reply-To: <CAG48ez3X3aZwfde3_2Sc+gdtUGRHfzan6oNFiffAvNzFDSsFDw@mail.gmail.com>

On Wed, Sep 30, 2020 at 11:10:43PM +0200, Jann Horn wrote:
> On Wed, Sep 30, 2020 at 11:02 PM Gustavo A. R. Silva
> <gustavoars@kernel.org> wrote:
> > There is a regular need in the kernel to provide a way to declare having
> > a dynamically sized set of trailing elements in a structure. Kernel code
> > should always use “flexible array members”[1] for these cases. The older
> > style of one-element or zero-length arrays should no longer be used[2].
> 
> But this is not such a case, right? Isn't this a true fixed-size
> array? It sounds like you're just changing it because it
> pattern-matched on "array of length 1 at the end of a struct".

Yeah; I should have changed that 'dynamically' part of the text above
a bit. However, as I commented in the text below, in the case that more
CS IDs are needed (let's wait for the maintainers to comment on this...)
in the future, this change makes the code more maintainable, as for
the allocation part, the developer would only have to update the CS_N
macro to the number of CS IDs that are needed.

Thanks
--
Gustavo

> 
> > Refactor the code according to the use of a flexible-array member
> > instead of a one-element array. Also, make use of the struct_size()
> > helper to calculate the size of the allocation for _nand_. In order
> > to keep the code as maintainable as possible and to keep _cs_ as an
> > array, add a new macro CS_N to aid in the allocation size calculation,
> > in case there is a need for more Chip Select IDs in the future. In the
> > meantime, the macro is set to 1. This also avoids having to use a magic
> > number '1' as the last argument for struct_size().
> [...]
> > diff --git a/drivers/mtd/nand/raw/tegra_nand.c b/drivers/mtd/nand/raw/tegra_nand.c
> [...]
> > +/* Number of Chip Selects. Currently, only one. */
> > +#define CS_N                   1
> > +
> >  struct tegra_nand_controller {
> >         struct nand_controller controller;
> >         struct device *dev;
> > @@ -183,7 +186,7 @@ struct tegra_nand_chip {
> >         u32 config;
> >         u32 config_ecc;
> >         u32 bch_config;
> > -       int cs[1];
> > +       int cs[];
> >  };
> [...]

  reply	other threads:[~2020-09-30 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 21:08 [PATCH][next] mtd: rawnand: Replace one-element array with flexible-array member Gustavo A. R. Silva
2020-09-30 21:10 ` Jann Horn
2020-09-30 21:36   ` Gustavo A. R. Silva [this message]
2020-09-30 22:32     ` Jann Horn
2020-10-01  8:12       ` Miquel Raynal
2020-10-01  9:21         ` Stefan Agner

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=20200930213634.GA12855@embeddedor \
    --to=gustavoars@kernel.org \
    --cc=dev@lynxeye.de \
    --cc=jannh@google.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=stefan@agner.ch \
    --cc=thierry.reding@gmail.com \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).