From: Thomas Monjalon <thomas@monjalon.net>
To: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/3] ethdev: fix null pointer checking
Date: Wed, 03 Apr 2019 18:27:51 +0200 [thread overview]
Message-ID: <1807422.QXMQecOh3y@xps> (raw)
In-Reply-To: <20190403160726.1231-1-mohammad.abdul.awal@intel.com>
03/04/2019 18:07, Mohammad Abdul Awal:
> Null value for parameter name will cause segfault for the
> strnlen and strcmp functions.
I'm not sure we want such obvious checks for all APIs.
Here I would say yes.
> Fixes: 0b33b68d12 ("ethdev: export allocate function")
> Fixes: 942661004c ("ethdev: export secondary attach function")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
> ---
> --- a/lib/librte_ethdev/rte_ethdev.c
> +++ b/lib/librte_ethdev/rte_ethdev.c
> @@ -440,6 +440,11 @@ rte_eth_dev_allocate(const char *name)
> struct rte_eth_dev *eth_dev = NULL;
> size_t name_len;
>
> + if (name == NULL) {
> + RTE_ETHDEV_LOG(ERR, "Null pointer is specified\n");
This is a very generic error message.
It might be "Fail to allocate port with empty name"
> @@ -492,6 +497,11 @@ rte_eth_dev_attach_secondary(const char *name)
> uint16_t i;
> struct rte_eth_dev *eth_dev = NULL;
>
> + if (name == NULL) {
> + RTE_ETHDEV_LOG(ERR, "Null pointer is specified\n");
"Fail to attach port with empty name"
next prev parent reply other threads:[~2019-04-03 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:07 Mohammad Abdul Awal
2019-04-03 16:27 ` Thomas Monjalon [this message]
2019-04-03 16:35 ` Ferruh Yigit
2019-04-03 16:41 ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2019-04-03 16:52 ` Ferruh Yigit
2019-04-03 17:32 ` David Marchand
2019-04-04 8:33 ` Mohammad Abdul Awal
2019-04-03 17:30 ` [dpdk-stable] " Awal, Mohammad Abdul
2019-04-03 18:42 ` Thomas Monjalon
2019-04-03 18:50 ` [dpdk-stable] [dpdk-dev] " Stephen Hemminger
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=1807422.QXMQecOh3y@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=stable@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).