From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/5] Fixes for build with -Dsanitize=undefined
Date: Thu, 19 Dec 2024 14:49:50 -0800 [thread overview]
Message-ID: <20241219225253.782792-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20241218170530.140747-1-stephen@networkplumber.org>
Recent bug report https://bugs.dpdk.org/show_bug.cgi?id=1605
highlighted that no build is done with -Dsanitize=address,undefined.
Doing a test build showed some new issues that were not being reported.
Note: a couple of these required introducing the equivalent _FOREACH_SAFE
variant macros. These are in FreeBSD and in DPDK windows versions of queue.h
but never made it to Linux sys/queue.h. Put the macro in the file where
used (rather than a common spot) to make backporting the fixes easier.
Stephen Hemminger (5):
bus/fslmc: fix use after rte_free
net/bnxt: fix use after free
net/bnx2x: use RTE_BIT32
net/qede: fix use after free
vhost: use strlcpy instead of strncpy
drivers/bus/fslmc/portal/dpaa2_hw_dpio.c | 3 +-
drivers/net/bnx2x/ecore_reg.h | 130 +++++++++++------------
drivers/net/bnxt/bnxt_filter.c | 11 +-
drivers/net/qede/qede_filter.c | 20 ++--
lib/vhost/socket.c | 3 +-
5 files changed, 90 insertions(+), 77 deletions(-)
--
2.45.2
next prev parent reply other threads:[~2024-12-19 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 17:05 [PATCH] bus/fslmc: fix use after rte_free Stephen Hemminger
2024-12-19 22:49 ` Stephen Hemminger [this message]
2024-12-19 22:49 ` [PATCH v2 1/5] " Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 2/5] net/bnxt: fix use after free Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 3/5] net/bnx2x: use RTE_BIT32 Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 4/5] net/qede: fix use after free Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 5/5] vhost: use strlcpy instead of strncpy Stephen Hemminger
2024-12-20 13:37 ` Bruce Richardson
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=20241219225253.782792-1-stephen@networkplumber.org \
--to=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).