DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, stable@dpdk.org,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	 Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
	 Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>,
	 Mike Baucom <michael.baucom@broadcom.com>
Subject: Re: [PATCH] net/bnxt: fix unintialized warning
Date: Fri, 21 Nov 2025 11:24:33 -0800	[thread overview]
Message-ID: <CACZ4nhve0VGWbhxZ_f8NxG471Sjdd+Cfp0OcHcahN2Uqvik3rA@mail.gmail.com> (raw)
In-Reply-To: <20251114185240.1363648-1-stephen@networkplumber.org>

[-- Attachment #1: Type: text/plain, Size: 3195 bytes --]

On Fri, Nov 14, 2025 at 10:52 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> With gcc-16 it inlines a lot more code and creates a warnings
> where it thinks it might be manipulating bits that are not set.
> It looks like this is because the bits in control word (cword)
> in theory could be larger than the variable. Should not
> be possible because wc_ctl_size_bits is only set to 3, 16, or 32
> but that happens outside of the scope of these functions.
>
> Resolve by adding bounds check which compiler sees and knows
> the loop will only see those bits.
>
> In function ‘ulp_bs_push_msb’,
>     inlined from ‘ulp_blob_push’ at ../drivers/net/bnxt/tf_ulp/ulp_utils.h:407:8,
>     inlined from ‘ulp_blob_push_32’ at ../drivers/net/bnxt/tf_ulp/ulp_utils.h:551:7,
>     inlined from ‘ulp_mapper_wc_tcam_tbl_dyn_post_process’ at ../drivers/net/bnxt/tf_ulp/ulp_mapper.c:2487:9:
> ../drivers/net/bnxt/tf_ulp/ulp_utils.h:336:17: warning: ‘cword’ may be used uninitialized [-Wmaybe-uninitialized]
>   336 |                 ulp_bs_put_msb(bs, pos, 8, val[i]);
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../drivers/net/bnxt/tf_ulp/ulp_mapper.c: In function ‘ulp_mapper_wc_tcam_tbl_dyn_post_process’:
> ../drivers/net/bnxt/tf_ulp/ulp_mapper.c:2443:18: note: ‘cword’ declared here
>  2443 |         uint32_t cword, i, rc;
>       |                  ^~~~~
>
> Bugzilla ID: 1821
> Fixes: 3fe124d2536c ("net/bnxt: support Thor platform")
> Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

> ---
>  drivers/net/bnxt/tf_ulp/ulp_mapper.c     | 5 +++++
>  drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c | 4 ++++
>  2 files changed, 9 insertions(+)
>
> diff --git a/drivers/net/bnxt/tf_ulp/ulp_mapper.c b/drivers/net/bnxt/tf_ulp/ulp_mapper.c
> index 0ff952950b..960cdda311 100644
> --- a/drivers/net/bnxt/tf_ulp/ulp_mapper.c
> +++ b/drivers/net/bnxt/tf_ulp/ulp_mapper.c
> @@ -2446,6 +2446,11 @@ ulp_mapper_wc_tcam_tbl_dyn_post_process(struct bnxt_ulp_device_params *dparms,
>
>         slice_width = dparms->wc_slice_width;
>         clen = dparms->wc_ctl_size_bits;
> +       if (clen > 32) {
> +               BNXT_DRV_DBG(ERR, "Key size bits %d too large\n", clen);
> +               return -EINVAL;
> +       }
> +
>         max_slices = dparms->wc_max_slices;
>         blen = ulp_blob_data_len_get(key);
>
> diff --git a/drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c b/drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c
> index f99698a1d8..2d89f10d5e 100644
> --- a/drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c
> +++ b/drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c
> @@ -90,6 +90,10 @@ ulp_mapper_tfc_wc_tcam_post_process(struct bnxt_ulp_device_params *dparms,
>
>         slice_width = dparms->wc_slice_width;
>         clen = dparms->wc_ctl_size_bits;
> +       if (clen > 32) {
> +               BNXT_DRV_DBG(ERR, "Key size bits %d too large\n", clen);
> +               return -EINVAL;
> +       }
>         max_slices = dparms->wc_max_slices;
>         blen = ulp_blob_data_len_get(key);
>
> --
> 2.51.0
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5479 bytes --]

      reply	other threads:[~2025-11-21 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 18:52 Stephen Hemminger
2025-11-21 19:24 ` Ajit Khaparde [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=CACZ4nhve0VGWbhxZ_f8NxG471Sjdd+Cfp0OcHcahN2Uqvik3rA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=michael.baucom@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=venkatkumar.duvvuru@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).