From: Andrew Lunn <andrew@lunn.ch>
To: Tao Cui <cuitao@kylinos.cn>
Cc: leitao@debian.org, vadim.fedorenko@linux.dev,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2] net: ethtool: fix missing closing paren in rings_reply_size()
Date: Fri, 8 May 2026 14:07:04 +0200 [thread overview]
Message-ID: <1c5f2275-17f0-4a80-97db-61af3129e6b4@lunn.ch> (raw)
In-Reply-To: <20260508100435.186819-1-cuitao@kylinos.cn>
On Fri, May 08, 2026 at 06:04:35PM +0800, Tao Cui wrote:
> sizeof(u32) on the _RINGS_CQE_SIZE line is missing its closing
> parenthesis, causing nla_total_size() to absorb the subsequent
> _TX_PUSH and _RX_PUSH entries. The resulting size estimate
> happens to be numerically identical due to NLA alignment, but
> the nesting is wrong and misleading.
>
> Fixes: 4dc84c06a343 ("net: ethtool: extend ringparam set/get APIs for tx_push")
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
> Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> Reviewed-by: Breno Leitao <leitao@debian.org>
> ---
> v2:
> - Added Fixes: tag as suggested by Breno Leitao.
> - Added Reviewed-by tags from Vadim Fedorenko and Breno Leitao.
Please always start a new thread for a new version of a
patch. Otherwise the CI/CD system just thinks it is a comment to an
existing patch.
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
Andrew
next prev parent reply other threads:[~2026-05-08 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 7:14 [PATCH] net: ethtool: fix missing closing paren in rings_reply_size() Tao Cui
2026-05-08 9:30 ` Vadim Fedorenko
2026-05-08 9:33 ` Breno Leitao
2026-05-08 10:04 ` [PATCH net v2] " Tao Cui
2026-05-08 12:07 ` Andrew Lunn [this message]
2026-05-08 20:41 ` [PATCH] " Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2026-05-08 12:54 [PATCH net v2] " Tao Cui
2026-05-12 1:49 ` patchwork-bot+netdevbpf
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=1c5f2275-17f0-4a80-97db-61af3129e6b4@lunn.ch \
--to=andrew@lunn.ch \
--cc=cuitao@kylinos.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox