From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/4] Coverity issue fixes
Date: Tue, 6 Nov 2018 11:30:01 -0800 [thread overview]
Message-ID: <20181106193005.5383-1-stephen@networkplumber.org> (raw)
These are all error path issues and should not matter in
a real application; most of the error are impossible to cause
and applications just fail if setup fails.
Stephen Hemminger (4):
net/failsafe: avoid rte_memcpy if rte_realloc fails
bus/vmbus: fix directory handle leak on error
net/tap: fix file descriptor leak on error
net/tap: fix warning about comparison of fd
drivers/bus/vmbus/linux/vmbus_uio.c | 12 +++++++-----
drivers/net/failsafe/failsafe_ops.c | 2 +-
drivers/net/tap/rte_eth_tap.c | 2 +-
drivers/net/tap/tap_netlink.c | 3 +++
4 files changed, 12 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-06 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 19:30 Stephen Hemminger [this message]
2018-11-06 19:30 ` [dpdk-dev] [PATCH 1/4] net/failsafe: avoid rte_memcpy if rte_realloc fails Stephen Hemminger
2018-11-07 6:30 ` Andrew Rybchenko
2018-11-07 18:15 ` Stephen Hemminger
2018-11-08 6:20 ` Andrew Rybchenko
2018-11-06 19:30 ` [dpdk-dev] [PATCH 2/4] bus/vmbus: fix directory handle leak on error Stephen Hemminger
2018-11-06 19:30 ` [dpdk-dev] [PATCH 3/4] net/tap: fix file descriptor " Stephen Hemminger
2018-11-07 10:02 ` Wiles, Keith
2018-11-06 19:30 ` [dpdk-dev] [PATCH 4/4] net/tap: fix warning about comparison of fd Stephen Hemminger
2018-11-07 10:03 ` Wiles, Keith
2018-11-14 1:00 ` [dpdk-dev] [PATCH 0/4] Coverity issue fixes 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=20181106193005.5383-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).