From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1710] net/bnxt build failure with LTO enabled
Date: Mon, 19 Jan 2026 18:47:09 +0000 [thread overview]
Message-ID: <bug-1710-3-pSsqkRBL08@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1710-3@http.bugs.dpdk.org/>
http://bugs.dpdk.org/show_bug.cgi?id=1710
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Stephen Hemminger (stephen@networkplumber.org) ---
Fixed by
commit 49b1673ec6693a673b4dc07984023f481cce4d96
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed May 21 12:37:27 2025 -0700
net/bnxt: fix free of not allocated object
This was found as error when compiling with LTO.
The function allocates new data with rte_zmalloc and then
stores pointer in the pointer-to-pointer passed as argument.
In the unwind case, it would call rte_free() with wrong one.
Fixes: 80317ff6adfd ("net/bnxt/tf_core: support Thor2")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-01-19 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 15:21 [DPDK/ethdev Bug 1710] net/bnxt build failure with LTO enabled bugzilla
2026-01-19 18:47 ` bugzilla [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=bug-1710-3-pSsqkRBL08@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox