From: Denis Sergeev <denserg.edu@gmail.com>
To: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
Cc: dev@dpdk.org, ajit.khaparde@broadcom.com, stable@dpdk.org
Subject: Re: [PATCH 1/2] net/bnxt/tf_core: fix ignored return of EM delete
Date: Wed, 3 Jun 2026 06:57:01 +0300 [thread overview]
Message-ID: <a53fce43-d572-4f93-bd8f-1d38fd08a229@gmail.com> (raw)
In-Reply-To: <CA+BST0nKjhifTBgKgn7qjb2oGEb7XFq3Ejr75u0T9Lm_c0p1EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
On 5/20/26 12:02 AM, Kishore Padmanabha wrote:
>
> On Tue, May 19, 2026 at 12:44 AM Denis Sergeev <denserg.edu@gmail.com>
> wrote:
>
> The return value of tfc_em_delete_raw() in tfc_em_delete() was
> silently discarded: rc was unconditionally overwritten by the
> subsequent tfc_cpm_get_cmm_inst() call without any error check.
>
> If tfc_em_delete_raw() fails, the HW EM entry is not removed but
> the function continues to free the corresponding SW pool entry,
> creating a HW/SW state inconsistency that can lead to stale flow
> matches or incorrect pool slot reuse.
>
> Add an error check after the call and return -EINVAL on failure.
>
> Found by Linux Verification Center (linuxtesting.org
> <http://linuxtesting.org>) with SVACE.
>
> Fixes: 80317ff6adfd ("net/bnxt/tf_core: support Thor2")
> Cc: stable@dpdk.org
>
> Signed-off-by: Denis Sergeev <denserg.edu@gmail.com>
> ---
> drivers/net/bnxt/tf_core/v3/tfc_em.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/bnxt/tf_core/v3/tfc_em.c
> b/drivers/net/bnxt/tf_core/v3/tfc_em.c
> index 3fe4dbe3fe..4c126dc2f4 100644
> --- a/drivers/net/bnxt/tf_core/v3/tfc_em.c
> +++ b/drivers/net/bnxt/tf_core/v3/tfc_em.c
> @@ -661,6 +661,11 @@ int tfc_em_delete(struct tfc *tfcp, struct
> tfc_em_delete_parms *parms)
> &db_offset
> #endif
> );
> + if (rc != 0) {
> + PMD_DRV_LOG_LINE(ERR, "tfc_em_delete_raw() failed:
> %s",
> + strerror(-rc));
> + return -EINVAL;
> + }
>
> record_offset = REMOVE_POOL_FROM_OFFSET(pi.lkup_pool_sz_exp,
> record_offset);
>
> This change is not required, even if deletion of the HW entry fails,
> it should continue to delete the SW state, since at the end all the HW
> entries are invalidated. Have you been able to reproduce a scenario
> where this failure is seen.
>
> --
> 2.50.1
>
Thanks for the review. I'll drop this patch.
The issue was flagged by a static analyzer that caught the discarded
return value of tfc_em_delete_raw(). Over the past week I tried to
reproduce an actual failure at runtime, but I couldn't. So it seems
this failure doesn't occur in real runtime.
--
Best regards,
Denis Sergeev
[-- Attachment #2: Type: text/html, Size: 4428 bytes --]
next prev parent reply other threads:[~2026-06-03 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 4:43 [PATCH 0/2] net/bnxt/tf_core: fix ignored return of EM delete Denis Sergeev
2026-05-19 4:43 ` [PATCH 1/2] " Denis Sergeev
2026-05-19 21:02 ` Kishore Padmanabha
2026-06-03 3:57 ` Denis Sergeev [this message]
2026-05-19 4:43 ` [PATCH 2/2] mailmap: add Denis Sergeev Denis Sergeev
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=a53fce43-d572-4f93-bd8f-1d38fd08a229@gmail.com \
--to=denserg.edu@gmail.com \
--cc=ajit.khaparde@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