From: Danilo Krummrich <dakr@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Lyude Paul <lyude@redhat.com>, David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] drm/nouveau/outp: Avoid -Wflex-array-member-not-at-end warning
Date: Fri, 28 Mar 2025 16:05:38 +0100 [thread overview]
Message-ID: <Z-a6wtoIAkDY2ERx@pollux> (raw)
In-Reply-To: <Z-a2DAQmcsHHlyci@kspp>
On Fri, Mar 28, 2025 at 08:45:32AM -0600, 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.
>
> Use the `DEFINE_RAW_FLEX()` helper for an on-stack definition of
> a flexible structure where the size of the flexible-array member
> is known at compile-time, and refactor the rest of the code,
> accordingly.
>
> So, with these changes, fix the following warning:
>
> drivers/gpu/drm/nouveau/nvif/outp.c:199:45: warning: structure containing a flexible array member is not at the end of another structure [-Wflex-array-member-not-at-end]
>
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> ---
> drivers/gpu/drm/nouveau/nvif/outp.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nvif/outp.c b/drivers/gpu/drm/nouveau/nvif/outp.c
> index 6daeb7f0b09b..403cf16d5e84 100644
> --- a/drivers/gpu/drm/nouveau/nvif/outp.c
> +++ b/drivers/gpu/drm/nouveau/nvif/outp.c
> @@ -195,20 +195,18 @@ nvif_outp_dp_aux_pwr(struct nvif_outp *outp, bool enable)
> int
> nvif_outp_hda_eld(struct nvif_outp *outp, int head, void *data, u32 size)
> {
> - struct {
> - struct nvif_outp_hda_eld_v0 mthd;
> - u8 data[128];
> - } args;
> + DEFINE_RAW_FLEX(struct nvif_outp_hda_eld_v0, mthd, data, 128);
> int ret;
>
> - if (WARN_ON(size > ARRAY_SIZE(args.data)))
> + if (WARN_ON(size > 128))
Seems a bit unfortunate that the size is duplicated here.
Can we have an accessor macro to derive the size for us?
union {
u8 bytes[struct_size_t(type, member, count)];
type obj;
} name##_u initializer;
Maybe a macro that returns the size difference between bytes and obj?
> return -EINVAL;
>
> - args.mthd.version = 0;
> - args.mthd.head = head;
> + mthd->version = 0;
> + mthd->head = head;
>
> - memcpy(args.data, data, size);
> - ret = nvif_mthd(&outp->object, NVIF_OUTP_V0_HDA_ELD, &args, sizeof(args.mthd) + size);
> + memcpy(mthd->data, data, size);
> + ret = nvif_mthd(&outp->object, NVIF_OUTP_V0_HDA_ELD, mthd,
> + __struct_size(mthd) + size);
> NVIF_ERRON(ret, &outp->object, "[HDA_ELD head:%d size:%d]", head, size);
> return ret;
> }
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-03-28 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 14:45 [PATCH][next] drm/nouveau/outp: Avoid -Wflex-array-member-not-at-end warning Gustavo A. R. Silva
2025-03-28 15:05 ` Danilo Krummrich [this message]
2025-03-28 15:44 ` Gustavo A. R. Silva
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=Z-a6wtoIAkDY2ERx@pollux \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
/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