From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Zhu Yanjun <yanjun.zhu@linux.dev>,
linux-rdma@vger.kernel.org, lirongqing <lirongqing@baidu.com>
Subject: Re: [PATCH] RDMA/mlx5: Restore flow_attr-first layout in leftovers flow rules
Date: Wed, 23 Sep 2026 12:45:43 -0300 [thread overview]
Message-ID: <20260923154543.GI1540250@ziepe.ca> (raw)
In-Reply-To: <20260923124547.GR563127@unreal>
On Wed, Sep 23, 2026 at 03:45:47PM +0300, Leon Romanovsky wrote:
> On Wed, Sep 23, 2026 at 08:41:48AM -0400, Leon Romanovsky wrote:
> >
> > On Thu, 17 Sep 2026 19:17:22 +0800, lirongqing wrote:
> > > Commit e91fb8b9d0ed ("RDMA/mlx5: Avoid flexible array warning") split
> > > the leftovers_specs[] array into two separate structs to silence the
> > > "array of flexible structures" sparse warning, but in doing so
> > > reversed the member order: eth_flow was placed before flow_attr.
> > >
> > > _create_flow_rule() locates the flow specs with:
> > >
> > > [...]
> >
> > Applied, thanks!
>
> I dropped it, as it causes to flex array errors to return.
Yeah, but the bug is real..
There is a macro for this case:
static TRAILING_OVERLAP(struct ib_flow_attr, flow_attr, flows,
struct ib_flow_spec_eth eth_flow;
) leftovers_wc = { .flow_attr = { .num_of_specs = 1,
Jason
prev parent reply other threads:[~2026-09-23 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:17 [PATCH] RDMA/mlx5: Restore flow_attr-first layout in leftovers flow rules lirongqing
2026-09-17 11:25 ` sashiko-bot
2026-09-18 6:55 ` 答复: " Li,Rongqing
2026-09-23 12:41 ` Leon Romanovsky
2026-09-23 12:45 ` Leon Romanovsky
2026-09-23 15:45 ` Jason Gunthorpe [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=20260923154543.GI1540250@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=yanjun.zhu@linux.dev \
/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.