[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRIoufDcyohFWQz1@Asurada-Nvidia>
Date: Mon, 10 Nov 2025 10:02:33 -0800
From: Nicolin Chen <nicolinc@...dia.com>
To: "Gustavo A. R. Silva" <gustavoars@...nel.org>
CC: Jason Gunthorpe <jgg@...pe.ca>, Kevin Tian <kevin.tian@...el.com>, "Joerg
Roedel" <joro@...tes.org>, Will Deacon <will@...nel.org>, Robin Murphy
<robin.murphy@....com>, <iommu@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>, <linux-hardening@...r.kernel.org>
Subject: Re: [PATCH][next] iommufd/iommufd_private.h: Avoid
-Wflex-array-member-not-at-end warning
On Mon, Nov 10, 2025 at 08:35:31PM +0900, 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.
>
> Move the conflicting declaration to the end of the corresponding
> structure. Notice that struct iommufd_vevent is a flexible
> structure, this is a structure that contains a flexible-array
> member.
>
> Fix the following warning:
>
> drivers/iommu/iommufd/iommufd_private.h:621:31: warning: structure containing a flexible array member is not at the end of another structure [-Wflex-array-member-not-at-end]
IIUIC, there might be data corruption due to this? If so, I think
we should do:
[PATCH rc] iommufd: Fix flex-array-member-not-at-end in struct iommufd_veventq
And add:
Fixes: e36ba5ab808e ("iommufd: Add IOMMUFD_OBJ_VEVENTQ and IOMMUFD_CMD_VEVENTQ_ALLOC")
Cc: stable@...r.kernel.org
> Signed-off-by: Gustavo A. R. Silva <gustavoars@...nel.org>
With that,
Reviewed-by: Nicolin Chen <nicolinc@...dia.com>
Thanks for the patch!
Powered by blists - more mailing lists