From: Stephen Hemminger <stephen@networkplumber.org>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Shuanglin Wang <shuanglin.wang@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
Peter Spreadborough <peter.spreadborough@broadcom.com>
Subject: Re: [PATCH 2/4] net/bnxt: fix uninitialized read
Date: Thu, 12 Mar 2026 09:57:22 -0700 [thread overview]
Message-ID: <20260312095722.54ecf61d@phoenix.local> (raw)
In-Reply-To: <20260312103606.702617-3-ktraynor@redhat.com>
On Thu, 12 Mar 2026 10:36:04 +0000
Kevin Traynor <ktraynor@redhat.com> wrote:
> batch_info->enabled is read in tfc_mpc_batch_start() before it is
> initialized.
>
> Initialize batch_info to avoid this.
>
> Fixes: 67ad40007cd6 ("net/bnxt/tf_ulp: fix VFR cleanup and stats lockup")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
This needs to go through next-net-brcm so will delegate it.
next prev parent reply other threads:[~2026-03-12 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 10:36 [PATCH 0/4] Static analysis fixes Kevin Traynor
2026-03-12 10:36 ` [PATCH 1/4] vhost: fix resource leak Kevin Traynor
2026-03-17 14:46 ` Maxime Coquelin
2026-03-12 10:36 ` [PATCH 2/4] net/bnxt: fix uninitialized read Kevin Traynor
2026-03-12 16:57 ` Stephen Hemminger [this message]
2026-03-16 18:39 ` Thomas Monjalon
2026-03-12 18:45 ` Kishore Padmanabha
2026-03-12 10:36 ` [PATCH 3/4] app/testpmd: check for no arguments Kevin Traynor
2026-03-12 12:37 ` fengchengwen
2026-03-12 17:03 ` Stephen Hemminger
2026-03-12 23:59 ` fengchengwen
2026-03-13 9:24 ` Kevin Traynor
2026-03-14 7:57 ` fengchengwen
2026-03-16 9:47 ` Kevin Traynor
2026-03-12 10:36 ` [PATCH 4/4] app/testpmd: fix fd leak Kevin Traynor
2026-03-17 15:52 ` Thomas Monjalon
2026-03-17 15:55 ` [PATCH 0/4] Static analysis fixes Thomas Monjalon
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=20260312095722.54ecf61d@phoenix.local \
--to=stephen@networkplumber.org \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kishore.padmanabha@broadcom.com \
--cc=ktraynor@redhat.com \
--cc=peter.spreadborough@broadcom.com \
--cc=shuanglin.wang@broadcom.com \
--cc=sriharsha.basavapatna@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.