DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 2115] net/ntnic: mulitple issues detected with GCC -fanalyzer
Date: Thu, 12 Nov 2026 17:42:45 +0000	[thread overview]
Message-ID: <bug-2115-3@https.bugs.dpdk.org/> (raw)

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

            Bug ID: 2115
           Summary: net/ntnic: mulitple issues detected with GCC
                    -fanalyzer
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

23. net/ntnic: FPGA model constructors return unchecked malloc
Component: ethdev | Severity: minor | Confidence: single pass

nthw_fpga_model_new, nthw_module_new, nthw_register_new, nthw_field_new,
nthw_param_new (drivers/net/ntnic/nthw/model/nthw_fpga_model.c) return malloc()
directly and callers pass the result to *_init(), which dereferences it (:186,
:245, :296, :317, :418). Same in nthw_id_table_create()
(nthw/flow_api/flow_id_table.c:68, calloc dereferenced at :70).

24. net/ntnic: p_drv leaked on init failure
Component: ethdev | Severity: minor | Confidence: single pass

nthw_pci_dev_init() allocates p_drv at drivers/net/ntnic/ntnic_ethdev.c:2326
and stores it with store_pdrv() (:2380). The later return -1 paths (:2388,
:2437, :2456, ...) do not free it or clear the stored pointer.

25. net/ntnic: NULL check after dereference in nthw_pci_dev_deinit()
Component: ethdev | Severity: trivial | Confidence: confirmed

drivers/net/ntnic/ntnic_ethdev.c:2680 dereferences internals; :2688 then loops
on while (internals).

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2026-11-12 17:42 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-2115-3@https.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox