All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 980] bnxt: use of uninitalized data
Date: Thu, 24 Mar 2022 15:14:39 +0000	[thread overview]
Message-ID: <bug-980-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=980

            Bug ID: 980
           Summary: bnxt: use of uninitalized data
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: ajit.khaparde@broadcom.com
          Reporter: david.marchand@redhat.com
                CC: dev@dpdk.org
  Target Milestone: ---

This has been reported by covscan in our internal CI for v21.11:

1. dpdk-21.11/drivers/net/bnxt/tf_ulp/ulp_mapper.c:1745: var_decl: Declaring
variable "fid_parms" without initializer.
8. dpdk-21.11/drivers/net/bnxt/tf_ulp/ulp_mapper.c:1783: uninit_use_in_call:
Using uninitialized value "fid_parms.resource_sub_type" when calling
"ulp_mapper_fdb_opc_process".
9. dpdk-21.11/drivers/net/bnxt/tf_ulp/ulp_mapper.c:1783: uninit_use_in_call:
Using uninitialized value "fid_parms.fdb_flags" when calling
"ulp_mapper_fdb_opc_process".
#  1781|        ulp_flow_db_shared_session_set(&fid_parms,
tbl->shared_session);
#  1782|   
#  1783|->      rc = ulp_mapper_fdb_opc_process(parms, tbl, &fid_parms);
#  1784|        if (rc)
#  1785|                BNXT_TF_DBG(ERR, "Fail to link res to flow rc = %d\n",
rc);

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2022-03-24 15:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-980-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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.