From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net
Subject: [PATCH v2] Coverity fixes for EAL
Date: Wed, 25 Apr 2018 11:08:12 +0100 [thread overview]
Message-ID: <cover.1524650784.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1523977960.git.anatoly.burakov@intel.com>
This patchset fixes a few Coverity fixes in EAL introduced
by recent DPDK memory hotplug patchset.
Coverity issues fixed:
- 272607 - error condition not handled
Coverity issues not fixed:
- 272600 - negative return not handled
- Proper usage of API guarantees no negative return
One of existing coverity issues is not fixed by this patchset:
- 272585 - memory leak
due to being independently discovered and addressed in a
separate patch [1].
[1] http://dpdk.org/dev/patchwork/patch/38301/
v2:
- Dropped fix for 272600 and marked it as false positive
Anatoly Burakov (1):
eal: remove call to unlock
lib/librte_eal/linuxapp/eal/eal_hugepage_info.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2018-04-25 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:42 [PATCH 0/2] Coverity fixes for EAL Anatoly Burakov
2018-04-17 15:42 ` [PATCH 1/2] eal: fix potential negative return Anatoly Burakov
2018-04-25 5:55 ` Tan, Jianfeng
2018-04-17 15:42 ` [PATCH 2/2] eal: fix not checking unlock result Anatoly Burakov
2018-04-25 7:09 ` Tan, Jianfeng
2018-04-25 8:53 ` Burakov, Anatoly
2018-04-25 10:08 ` Anatoly Burakov [this message]
2018-04-25 10:08 ` [PATCH v2] eal: remove call to unlock Anatoly Burakov
2018-04-25 10:32 ` 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=cover.1524650784.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.