From: Kees Cook <kees@kernel.org>
To: Alison Schofield <alison.schofield@intel.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
justinstitt@google.com, Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
nvdimm@lists.linux.dev, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] UAPI: ndctl / acpi: intel: Avoid multiple -Wflex-array-member-not-at-end warnings
Date: Tue, 6 May 2025 11:37:28 -0700 [thread overview]
Message-ID: <202505061135.C76B6CA9F@keescook> (raw)
In-Reply-To: <202504071106.3A0AF875F@keescook>
On Mon, Apr 07, 2025 at 11:11:08AM -0700, Kees Cook wrote:
> On Thu, Feb 13, 2025 at 02:25:27PM -0800, Alison Schofield wrote:
> > On Thu, Feb 13, 2025 at 03:29:12PM +1030, Gustavo A. R. Silva wrote:
> > > -Wflex-array-member-not-at-end was introduced in GCC-14, and we are
> > > getting ready to enable it, globally.
> > >
> > > So, in order to avoid ending up with flexible-array members in the
> > > middle of other structs, we use the `__struct_group()` helper to
> > > separate the flexible array from the rest of the members in the
> > > flexible structure. We then use the newly created tagged `struct
> > > nd_cmd_pkg_hdr` to replace the type of the objects causing trouble
> > > (`pkg`) in multiple structs.
> > >
> > > So, with these changes, fix the following warnings:
> > >
> > > drivers/acpi/nfit/intel.c:692:35: warning: structure containing a flexible array member is not at the end of another structure [-Wflex-array-member-not-at-end]
> >
> > One sample warning is good.
> >
> > How about adding a comment on why the usage of __struct_group() here
> > means this doesn't break userspace.
> >
> > snip
> >
> > > diff --git a/include/uapi/linux/ndctl.h b/include/uapi/linux/ndctl.h
> > > index 73516e263627..34c11644d5d7 100644
> > > --- a/include/uapi/linux/ndctl.h
> > > +++ b/include/uapi/linux/ndctl.h
> >
> > FWIW: In a patch like this where reviewers likely want to see
> > the header file change first, put it first in the diff.
> > (git diff.orderfile)
>
> TIL about diff.orderfile! :) Just for my own education, what do you have
> as the contents for your orderfile? Is it just simply:
>
> *.h
>
> ?
I've updated my local environment to use this, to see how well it ends up
behaving:
Kconfig
*/Kconfig
*/Kconfig.*
Makefile
*/Makefile
*/Makefile.*
scripts/*
Documentation/*
*.h
*.S
*.c
tools/testing/*
https://github.com/kees/kernel-tools/commit/909db155b5cd36832d10d7d9932d7b51b46388aa
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-05-06 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 4:59 [PATCH][next] UAPI: ndctl / acpi: intel: Avoid multiple -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-02-13 22:25 ` Alison Schofield
2025-04-07 18:11 ` Kees Cook
2025-04-07 19:09 ` Gustavo A. R. Silva
2025-05-06 18:37 ` Kees Cook [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=202505061135.C76B6CA9F@keescook \
--to=kees@kernel.org \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gustavoars@kernel.org \
--cc=ira.weiny@intel.com \
--cc=justinstitt@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=vishal.l.verma@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 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.