From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
To: dev@dpdk.org
Cc: kishore.padmanabha@broadcom.com,
Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>,
stable@dpdk.org, Dakota Sicher <dakota.sicher@broadcom.com>
Subject: [PATCH v2] net/bnxt: fix flow create segfault
Date: Sun, 20 Sep 2026 20:18:17 -0600 [thread overview]
Message-ID: <20260921021817.1033783-1-Mohammad-Shuab.Siddique@broadcom.com> (raw)
In-Reply-To: <20260918032701.763364-1-Mohammad-Shuab.Siddique@broadcom.com>
From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
When creating a flow that requires a destination queue but none is
specified in the flow create command, find_matching_vnic() returns
NULL and the code falls through to insert the new filter into
vnic->filter, dereferencing the NULL vnic and causing a segfault.
Check for a NULL vnic and reject the flow create with a clear error
instead of crashing.
Fixes: 59119d49529e ("net/bnxt: fix flow create when RSS is disabled")
Cc: stable@dpdk.org
Signed-off-by: Dakota Sicher <dakota.sicher@broadcom.com>
Signed-off-by: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
---
v2:
* Changed the new NULL check from "if (!vnic)" to "if (vnic == NULL)"
to match this file's established convention for pointer NULL checks
(e.g. the existing "if (vnic == NULL)" a few hundred lines above).
* Kept RTE_FLOW_ERROR_TYPE_HANDLE rather than RTE_FLOW_ERROR_TYPE_ACTION
as one reviewer suggested: every other rte_flow_error_set() call in
this same function (bnxt_flow_create()) uses
RTE_FLOW_ERROR_TYPE_HANDLE regardless of the underlying cause, so
switching just this one would be inconsistent with its neighbors.
* Real bug found during v2 review: the new branch didn't reset "ret"
before "goto free_filter". If bnxt_match_filter() had already set
update_flow (ret == -EXDEV) and the filter is a plain L2 filter, the
stale -EXDEV survived to the free_flow label and reported the
misleading "pattern exists, updating destination queue" success-like
error instead of the real failure. Now sets ret = -EINVAL on this
path, same as every other error branch in this function.
drivers/net/bnxt/bnxt_flow.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/net/bnxt/bnxt_flow.c b/drivers/net/bnxt/bnxt_flow.c
index a2e590540b..0a2899fbbd 100644
--- a/drivers/net/bnxt/bnxt_flow.c
+++ b/drivers/net/bnxt/bnxt_flow.c
@@ -2148,6 +2148,14 @@ bnxt_flow_create(struct rte_eth_dev *dev,
}
vnic = find_matching_vnic(bp, filter);
+ if (vnic == NULL) {
+ rte_flow_error_set(error, EINVAL,
+ RTE_FLOW_ERROR_TYPE_HANDLE, NULL,
+ "Missing destination action for flow.");
+ bnxt_clear_one_vnic_filter(bp, filter);
+ ret = -EINVAL;
+ goto free_filter;
+ }
done:
if (!ret || update_flow) {
flow->filter = filter;
--
2.47.3
next prev parent reply other threads:[~2026-09-21 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 3:27 [PATCH] net/bnxt: fix flow create segfault Mohammad Shuab Siddique
2026-09-21 2:18 ` Mohammad Shuab Siddique [this message]
2026-09-21 15:46 ` [PATCH v2] " Stephen Hemminger
2026-09-29 0:23 ` [PATCH v3] " Mohammad Shuab Siddique
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=20260921021817.1033783-1-Mohammad-Shuab.Siddique@broadcom.com \
--to=mohammad-shuab.siddique@broadcom.com \
--cc=dakota.sicher@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