dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Manish Kurup <manish.kurup@broadcom.com>
To: dev@dpdk.org
Cc: kishore.padmanabha@broadcom.com
Subject: [PATCH 0/2] net/bnxt: fix message layer and hot-upgrade issues
Date: Mon,  5 Oct 2026 10:16:57 -0500	[thread overview]
Message-ID: <20261005151659.1705967-1-manish.kurup@broadcom.com> (raw)

This series fixes several bounds/pointer issues found by static
analysis in the tf_core message layer, plus a related validation
limit bug found while fixing them:

- Patch 1 caps a memcpy() to the caller's buffer size in
  tfc_msg_idx_tbl_get(), adds a NULL check on that function's
  caller-supplied dev_data/data_size pointers, fixes a fall-through
  in tfc_msg_if_tbl_get() that let a size-mismatch error still copy
  oversized data, and adds missing NULL checks on a caller-supplied
  pointer in tfc_msg_idx_tbl_alloc_set()/tfc_msg_idx_tbl_set().

- Patch 2 fixes the app-instance-ID validation limit used during
  hot-upgrade: it enforced a limit of 4 (the number of concurrent
  instances) instead of 8 (the actual valid ID range), incorrectly
  rejecting valid instance IDs 5-8.

Manish Kurup (1):
  net/bnxt: fix hot-upgrade app instance ID limit

Mohammad Shuab Siddique (1):
  net/bnxt: fix message-layer bounds and pointer checks

 .../bnxt/hcapi/cfa_v3/include/cfa_resources.h |  2 +-
 drivers/net/bnxt/tf_core/v3/tfc_msg.c         | 32 ++++++++++++++++---
 2 files changed, 29 insertions(+), 5 deletions(-)

-- 
2.31.1


             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 Manish Kurup [this message]
2026-10-05 15:16 ` [PATCH 1/2] net/bnxt: fix message-layer bounds and pointer checks Manish Kurup
2026-10-05 15:16 ` [PATCH 2/2] net/bnxt: fix hot-upgrade app instance ID limit Manish Kurup

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-1-manish.kurup@broadcom.com \
    --to=manish.kurup@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.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;
as well as URLs for NNTP newsgroup(s).