From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>
Subject: [PATCH 00/16] verify strdup return value
Date: Fri, 10 Nov 2023 06:36:37 +0000 [thread overview]
Message-ID: <20231110063653.5948-1-fengchengwen@huawei.com> (raw)
This patchset mainly fix the return value of strdup not checked which
may lead to segment fault. It also include two commits which fix memory
leak of strdup.
Chengwen Feng (16):
eal: verify strdup return value
bus/dpaa: verify strdup return value
bus/fslmc: verify strdup return value
bus/vdev: verify strdup return value
dma/idxd: verify strdup return value
event/cnxk: verify strdup return value
net/failsafe: fix memory leak when parse args
net/nfp: verify strdup return value
app/dumpcap: verify strdup return value
app/pdump: verify strdup return value
app/test: verify strdup return value
app/test-crypto-perf: verify strdup return value
app/test-dma-perf: verify strdup return value
app/testpmd: verify strdup return value
examples/qos_sched: fix memory leak when parse args
examples/vhost: verify strdup return value
app/dumpcap/main.c | 5 ++++
app/pdump/main.c | 3 +++
app/test-crypto-perf/cperf_options_parsing.c | 4 ++++
app/test-dma-perf/main.c | 2 ++
app/test-pmd/cmdline.c | 2 ++
app/test/process.h | 5 +++-
drivers/bus/dpaa/dpaa_bus.c | 4 ++++
drivers/bus/fslmc/fslmc_bus.c | 4 ++++
drivers/bus/vdev/vdev.c | 4 ++++
drivers/dma/idxd/idxd_bus.c | 10 ++++++--
drivers/event/cnxk/cnxk_eventdev.c | 3 +++
drivers/net/failsafe/failsafe_args.c | 2 +-
drivers/net/nfp/nfp_ipsec.c | 5 ++++
examples/qos_sched/args.c | 4 +++-
examples/vhost/main.c | 3 +++
lib/eal/common/eal_common_options.c | 24 ++++++++++++++++++--
lib/eal/linux/eal_dev.c | 3 +++
17 files changed, 80 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2023-11-10 6:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 6:36 Chengwen Feng [this message]
2023-11-10 6:36 ` [PATCH 01/16] eal: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 02/16] bus/dpaa: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 03/16] bus/fslmc: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 04/16] bus/vdev: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 05/16] dma/idxd: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 06/16] event/cnxk: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 07/16] net/failsafe: fix memory leak when parse args Chengwen Feng
2023-11-10 6:36 ` [PATCH 08/16] net/nfp: verify strdup return value Chengwen Feng
2023-11-10 6:58 ` Chaoyong He
2023-11-10 6:36 ` [PATCH 09/16] app/dumpcap: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 10/16] app/pdump: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 11/16] app/test: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 12/16] app/test-crypto-perf: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 13/16] app/test-dma-perf: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 14/16] app/testpmd: " Chengwen Feng
2023-11-10 6:36 ` [PATCH 15/16] examples/qos_sched: fix memory leak when parse args Chengwen Feng
2023-11-10 6:36 ` [PATCH 16/16] examples/vhost: verify strdup return value Chengwen Feng
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=20231110063653.5948-1-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
/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).