From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: Re: [PATCH v3 1/1] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings
Date: Tue, 23 Dec 2025 08:13:49 -0800 [thread overview]
Message-ID: <ba0fb412-455b-4348-a81c-013e7f40377f@linux.dev> (raw)
In-Reply-To: <20251223142055.GC11869@unreal>
在 2025/12/23 6:20, Leon Romanovsky 写道:
> On Mon, Dec 22, 2025 at 09:10:11PM -0800, Zhu Yanjun wrote:
>> 在 2025/12/22 21:03, Gustavo A. R. Silva 写道:
>>>
>>> On 12/23/25 13:41, Zhu Yanjun wrote:
>>>> From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
>>>>
>>>> -Wflex-array-member-not-at-end was introduced in GCC-14, and we are
>>>> getting ready to enable it, globally.
>>>>
>>>> Use the new TRAILING_OVERLAP() helper to fix the following warning:
>>>>
>>>> 21 drivers/infiniband/sw/rxe/rxe_verbs.h:271:33: warning: structure
>>>> containing a flexible array member is not at the end of another
>>>> structure [-Wflex-array-member-not-at-end]
>>>>
>>>> This helper creates a union between a flexible-array member (FAM) and a
>>>> set of MEMBERS that would otherwise follow it.
>>>>
>>>> This overlays the trailing MEMBER struct ib_sge sge[RXE_MAX_SGE]; onto
>>>> the FAM struct rxe_recv_wqe::dma.sge, while keeping the FAM and the
>>>> start of MEMBER aligned.
>>>>
>>>> The static_assert() ensures this alignment remains, and it's
>>>> intentionally placed inmediately after the related structure --no
>>>> blank line in between.
>>>>
>>>> Lastly, move the conflicting declaration struct rxe_resp_info resp;
>>>> to the end of the corresponding structure.
>>>>
>>>> Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>>>> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>>>> ---
>>>> V2->V3: Replace struct ib_sge with struct rxe_sge
>>> What are you doing?
>> Because struct rxe_sge differs from struct ib_sge, I aligned it to use the
>> same structure.
> Zhu,
>
> Please submit your rxe_sge to ib_sge change as standalone patch and
> Gustavo will resubmit his patch later if he wants so.
OK. I will do soon.
Yanjun.Zhu
>
> Thanks
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2025-12-23 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 4:41 [PATCH v3 1/1] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings Zhu Yanjun
2025-12-23 5:03 ` Gustavo A. R. Silva
2025-12-23 5:10 ` Zhu Yanjun
2025-12-23 5:18 ` Gustavo A. R. Silva
2025-12-23 5:26 ` Zhu Yanjun
2025-12-23 5:34 ` Gustavo A. R. Silva
2025-12-23 5:44 ` Zhu Yanjun
2025-12-23 5:54 ` Gustavo A. R. Silva
2025-12-23 6:46 ` Zhu Yanjun
2025-12-23 9:28 ` Gustavo A. R. Silva
2025-12-23 16:02 ` Zhu Yanjun
2025-12-23 14:20 ` Leon Romanovsky
2025-12-23 16:13 ` Zhu Yanjun [this message]
2025-12-23 9:34 ` Gustavo A. R. Silva
2025-12-23 16:38 ` Greg Sword
2025-12-23 16:59 ` Gustavo A. R. Silva
2025-12-23 17:19 ` Greg Sword
2025-12-23 17:26 ` Gustavo A. R. Silva
2025-12-24 6:51 ` Leon Romanovsky
2025-12-24 8:32 ` 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=ba0fb412-455b-4348-a81c-013e7f40377f@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@gmail.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