From: Stephen Hemminger <stephen@networkplumber.org>
To: <ykanaujia@marvell.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>, <dev@dpdk.org>,
Satheesh Paul <psatheesh@marvell.com>
Subject: Re: [PATCH 1/2] common/cnxk: support aggregator enqueue profiles
Date: Wed, 23 Sep 2026 11:30:36 -0700 [thread overview]
Message-ID: <20260923113036.140e0a8f@phoenix.local> (raw)
In-Reply-To: <20260715084340.300442-1-ykanaujia@marvell.com>
On Wed, 15 Jul 2026 14:13:39 +0530
<ykanaujia@marvell.com> wrote:
> From: Satheesh Paul <psatheesh@marvell.com>
>
> Support for flow aggregator enqueue profiles.
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
This was merged to main without sufficient review.
AI review sees:
16f07d871f "common/cnxk: support aggregator enqueue profiles" — two real bugs:
1. roc_nix.c:533 — the new goto tm_conf_fini is the first error path placed after
nix->dev.drv_inited = true (line 526). It tears the device fully down but never
clears the flag, so a later roc_nix_dev_init on the same nix hits the early if
(nix->dev.drv_inited) return 0; at line 463 and reports success on a dead device.
Fix: move the cn20k call above the assignment, or clear the flag in the error
path. (The nix_list TAILQ entry is also leaked, but that's pre-existing on every
failure path — not this patch's regression.)
2. roc_nix.c:605 — struct nix_af_rx_flow_vec_ctrl_write_rsp is used but defined
nowhere in the tree. It compiles only because it's a pointer to an incomplete
type that's never dereferenced. The M() entry at roc_mbox.h:362 declares the
response as msg_rsp; the variable should be struct msg_rsp *.
Plus: if (rc) goto exit; immediately before exit: is a no-op; static (non-const)
arrays defined in roc_nix_flow_vec.h; 2021 copyright on a new file; one-line
commit message for a new mbox message and HW config path.
I checked and cleared the things that looked suspicious here: mbox ID 0x8034 is
unused, both bitfield unions total exactly 64 bits, every constant fits its
field, and memcpy sizes match the request array dimensions.
prev parent reply other threads:[~2026-09-23 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:43 [PATCH 1/2] common/cnxk: support aggregator enqueue profiles ykanaujia
2026-09-23 18:30 ` Stephen Hemminger [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=20260923113036.140e0a8f@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=ykanaujia@marvell.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