From: Praveen Shetty <praveen.shetty@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, pawelx.modrak@intel.com
Subject: [dpdk-dev] [PATCH v2] examples/ioat: resolve unchecked return value
Date: Thu, 28 Nov 2019 11:27:14 +0000 [thread overview]
Message-ID: <20191128112715.26283-1-praveen.shetty@intel.com> (raw)
In-Reply-To: <20191128100325.25003-1-praveen.shetty@intel.com>
patch checks the return value of function rte_eth_dev_info_get,
if return value is negative error message printed on the console.
Coverity issue: 350361
Fixes: c8e6ceecebc1 ("examples/ioat: add new sample app for ioat driver")
Cc: pawelx.modrak@intel.com
Signed-off-by: Praveen Shetty <praveen.shetty@intel.com>
---
examples/ioat/ioatfwd.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/examples/ioat/ioatfwd.c b/examples/ioat/ioatfwd.c
index e9117718f..b39a098ec 100644
--- a/examples/ioat/ioatfwd.c
+++ b/examples/ioat/ioatfwd.c
@@ -824,7 +824,11 @@ port_init(uint16_t portid, struct rte_mempool *mbuf_pool, uint16_t nb_queues)
/* Init port */
printf("Initializing port %u... ", portid);
fflush(stdout);
- rte_eth_dev_info_get(portid, &dev_info);
+ ret = rte_eth_dev_info_get(portid, &dev_info);
+ if (ret < 0)
+ rte_exit(EXIT_FAILURE, "Cannot get device info: %s, port=%u\n",
+ rte_strerror(-ret), portid);
+
local_port_conf.rx_adv_conf.rss_conf.rss_hf &=
dev_info.flow_type_rss_offloads;
if (dev_info.tx_offload_capa & DEV_TX_OFFLOAD_MBUF_FAST_FREE)
--
2.17.1
next prev parent reply other threads:[~2019-11-28 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 10:03 [dpdk-dev] [PATCH v1] " Praveen Shetty
2019-11-28 10:03 ` [dpdk-dev] [PATCH] " Praveen Shetty
2019-11-28 11:27 ` Praveen Shetty [this message]
2019-11-28 11:32 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2020-02-13 14:00 ` David Marchand
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=20191128112715.26283-1-praveen.shetty@intel.com \
--to=praveen.shetty@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pawelx.modrak@intel.com \
/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).