From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings
Date: Wed, 6 Mar 2024 10:10:30 +0900 [thread overview]
Message-ID: <20240306011030.GA71684@workstation.local> (raw)
In-Reply-To: <cover.1709658886.git.gustavoars@kernel.org>
Hi,
On Tue, Mar 05, 2024 at 11:24:15AM -0600, Gustavo A. R. Silva wrote:
> -Wflex-array-member-not-at-end is coming in GCC-14, and we are getting
> ready to enable it globally. So, we are deprecating flexible-array
> members in the middle of another struct.
>
> There are currently a couple of local structures (`u` and `template`)
> that are using a flexible `struct fw_iso_packet` as header for a couple
> of on-stack arrays.
>
> We make use of the `struct_group_tagged()` helper to separate the
> flexible array from the rest of the members in the flexible structure,
> and, with this, we can now declare objects of the type of the tagged
> struct, without embedding the flexible array in the middle of another
> struct.
>
> We also use `container_of()` whenever we need to retrieve a pointer to
> the flexible structure, through which the flexible-array member can be
> accessed.
>
> With these changes, we fix a couple of -Wflex-array-member-not-at-end
> warnings.
>
> Gustavo A. R. Silva (2):
> firewire: Avoid -Wflex-array-member-not-at-end warning
> ALSA: firewire-lib: Avoid -Wflex-array-member-not-at-end warning
>
> drivers/firewire/core-cdev.c | 9 +++++----
> include/linux/firewire.h | 16 +++++++++-------
> sound/firewire/amdtp-stream.c | 8 +++++---
> 3 files changed, 19 insertions(+), 14 deletions(-)
Thanks for the improvements, however we are mostly at the end of
development period for v6.8 kernel. Let me postpone applying the patches
until closing the next merge window (for v6.9), since we need the term to
evaluate the change. I mean that it goes to v6.10 kernel.
If you would like me to applying the patch v6.9 kernel, please inform it
to us.
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2024-03-06 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 17:24 [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2024-03-05 17:24 ` [PATCH 1/2][next] firewire: Avoid -Wflex-array-member-not-at-end warning Gustavo A. R. Silva
2024-03-05 17:25 ` [PATCH 2/2][next] ALSA: firewire-lib: " Gustavo A. R. Silva
2024-03-06 1:10 ` Takashi Sakamoto [this message]
2024-03-06 16:18 ` [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2024-04-29 18:30 ` Kees Cook
2024-04-29 18:42 ` Gustavo A. R. Silva
2024-04-29 19:50 ` Kees Cook
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=20240306011030.GA71684@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=perex@perex.cz \
--cc=tiwai@suse.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