From: Manish Kurup <manish.kurup@broadcom.com>
To: dev@dpdk.org
Cc: kishore.padmanabha@broadcom.com, stable@dpdk.org
Subject: [PATCH 2/2] net/bnxt: fix hot-upgrade app instance ID limit
Date: Mon, 5 Oct 2026 10:16:59 -0500 [thread overview]
Message-ID: <20261005151659.1705967-3-manish.kurup@broadcom.com> (raw)
In-Reply-To: <20261005151659.1705967-1-manish.kurup@broadcom.com>
CFA_HOT_UPGRADE_APP_INSTANCE_MAX (4) represents the max number of
concurrent hot-upgrade instances, not the max valid instance ID.
Valid instance IDs are 1-8, matching the existing devargs
validation, so tfc_hot_upgrade_validate()'s existing
app_inst_id > CFA_HOT_UPGRADE_APP_INSTANCE_MAX check rejects valid
IDs 5-8. Bump the constant to 8; the comparison itself is already
correct against the corrected limit.
Fixes: 80317ff6adfd ("net/bnxt/tf_core: support Thor2")
Cc: stable@dpdk.org
Signed-off-by: Manish Kurup <manish.kurup@broadcom.com>
---
drivers/net/bnxt/hcapi/cfa_v3/include/cfa_resources.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/bnxt/hcapi/cfa_v3/include/cfa_resources.h b/drivers/net/bnxt/hcapi/cfa_v3/include/cfa_resources.h
index ada9741dfa..98b96e0a11 100644
--- a/drivers/net/bnxt/hcapi/cfa_v3/include/cfa_resources.h
+++ b/drivers/net/bnxt/hcapi/cfa_v3/include/cfa_resources.h
@@ -194,7 +194,7 @@ enum cfa_resource_subtype_gim {
CFA_RSUBTYPE_SM_MAX + CFA_RSUBTYPE_TSM_MAX + CFA_RSUBTYPE_TIM_MAX + \
CFA_RSUBTYPE_GIM_MAX)
-#define CFA_HOT_UPGRADE_APP_INSTANCE_MAX 4
+#define CFA_HOT_UPGRADE_APP_INSTANCE_MAX 8
enum cfa_hot_upgrade_cmd_op {
CFA_HOT_UPGRADE_CMD_ALLOC = 1,
CFA_HOT_UPGRADE_CMD_FREE,
--
2.31.1
prev parent reply other threads:[~2026-10-05 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:16 [PATCH 0/2] net/bnxt: fix message layer and hot-upgrade issues Manish Kurup
2026-10-05 15:16 ` [PATCH 1/2] net/bnxt: fix message-layer bounds and pointer checks Manish Kurup
2026-10-05 15:16 ` Manish Kurup [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=20261005151659.1705967-3-manish.kurup@broadcom.com \
--to=manish.kurup@broadcom.com \
--cc=dev@dpdk.org \
--cc=kishore.padmanabha@broadcom.com \
--cc=stable@dpdk.org \
/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