From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/5] Fixes for issues highlighted by static analysis scan
Date: Tue, 16 Dec 2014 15:03:48 +0000 [thread overview]
Message-ID: <1418742233-16776-1-git-send-email-bruce.richardson@intel.com> (raw)
This patch set fixes 5 issues found during a static analysis scan of the latest
DPDK code. These fixes are for possible NULL pointer references and array
overflow/underflow.
Bruce Richardson (5):
test: after NULL check, don't free the NULL pointer
test: check for mbuf alloc failure
examples: set correct limit for length of unix socket path
examples: fix check for null before de-reference
cfgfile: prevent error when reading an empty file
app/test/test_kvargs.c | 3 ---
app/test/test_table_acl.c | 5 +++++
examples/vm_power_manager/channel_manager.c | 4 ++--
examples/vm_power_manager/channel_manager.h | 8 +++++++-
examples/vm_power_manager/vm_power_cli.c | 4 ++--
lib/librte_cfgfile/rte_cfgfile.c | 4 +++-
6 files changed, 19 insertions(+), 9 deletions(-)
--
1.9.3
next reply other threads:[~2014-12-16 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 15:03 Bruce Richardson [this message]
2014-12-16 15:03 ` [dpdk-dev] [PATCH 1/5] test: after NULL check, don't free the NULL pointer Bruce Richardson
2014-12-16 15:03 ` [dpdk-dev] [PATCH 2/5] test: check for mbuf alloc failure Bruce Richardson
2014-12-16 15:03 ` [dpdk-dev] [PATCH 3/5] examples: set correct limit for length of unix socket path Bruce Richardson
2014-12-16 15:03 ` [dpdk-dev] [PATCH 4/5] examples: fix check for null before de-reference Bruce Richardson
2014-12-16 15:03 ` [dpdk-dev] [PATCH 5/5] cfgfile: prevent error when reading an empty file Bruce Richardson
2014-12-16 23:53 ` [dpdk-dev] [PATCH 0/5] Fixes for issues highlighted by static analysis scan Thomas Monjalon
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=1418742233-16776-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--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).