DPDK patches and discussions
 help / color / mirror / Atom feed
From: wangyunjian <wangyunjian@huawei.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
	"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
	xudingke <xudingke@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix check of rx configure
Date: Wed, 4 Nov 2020 01:15:38 +0000	[thread overview]
Message-ID: <34EFBCA9F01B0748BEB6B629CE643AE60DAF1121@dggemm513-mbx.china.huawei.com> (raw)
In-Reply-To: <eca9ab73-96b4-146c-1e00-041dc93580d1@intel.com>

> -----Original Message-----
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Tuesday, November 3, 2020 9:58 PM
> To: wangyunjian <wangyunjian@huawei.com>; dev@dpdk.org
> Cc: thomas@monjalon.net; andrew.rybchenko@oktetlabs.ru; Lilijun (Jerry)
> <jerry.lilijun@huawei.com>; xudingke <xudingke@huawei.com>
> Subject: Re: [dpdk-dev] [PATCH] ethdev: fix check of rx configure
> 
> On 11/3/2020 1:31 PM, wangyunjian wrote:
> > From: Yunjian Wang <wangyunjian@huawei.com>
> >
> > Coverity flags that 'rx_conf' variable is used before it's checked for
> > NULL. This patch fixes this issue.
> >
> > Coverity issue: 363570
> > Fixes: 4ff702b5dfa9 ("ethdev: introduce Rx buffer split")
> >
> > Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> > ---
> >   lib/librte_ethdev/rte_ethdev.c | 9 +++++----
> >   1 file changed, 5 insertions(+), 4 deletions(-)
> >
> > diff --git a/lib/librte_ethdev/rte_ethdev.c
> > b/lib/librte_ethdev/rte_ethdev.c index b12bb3854d..c74502d45e 100644
> > --- a/lib/librte_ethdev/rte_ethdev.c
> > +++ b/lib/librte_ethdev/rte_ethdev.c
> > @@ -1978,16 +1978,17 @@ rte_eth_rx_queue_setup(uint16_t port_id,
> uint16_t rx_queue_id,
> >   			return -EINVAL;
> >   		}
> >   	} else {
> > -		const struct rte_eth_rxseg_split *rx_seg =
> > -			(const struct rte_eth_rxseg_split *)rx_conf->rx_seg;
> > -		uint16_t n_seg = rx_conf->rx_nseg;
> > -
> >   		/* Extended multi-segment configuration check. */
> >   		if (rx_conf == NULL || rx_conf->rx_seg == NULL ||
> rx_conf->rx_nseg == 0) {
> >   			RTE_ETHDEV_LOG(ERR,
> >   				       "Memory pool is null and no extended
> configuration provided\n");
> >   			return -EINVAL;
> >   		}
> > +
> > +		const struct rte_eth_rxseg_split *rx_seg =
> > +			(const struct rte_eth_rxseg_split *)rx_conf->rx_seg;
> > +		uint16_t n_seg = rx_conf->rx_nseg;
> > +
> 
> Can you please leave the declaration of the variables at the beginning of the
> block, but move the assignment?

OK, thanks for your suggestion, will include it in next version.

Yunjian

  reply	other threads:[~2020-11-04  1:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 13:31 wangyunjian
2020-11-03 13:58 ` Ferruh Yigit
2020-11-04  1:15   ` wangyunjian [this message]
2020-11-04  1:24 ` [dpdk-dev] [PATCH v2] " wangyunjian
2020-11-04 11:11   ` Ferruh Yigit
2020-11-04 11:22     ` Ferruh Yigit

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=34EFBCA9F01B0748BEB6B629CE643AE60DAF1121@dggemm513-mbx.china.huawei.com \
    --to=wangyunjian@huawei.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=thomas@monjalon.net \
    --cc=xudingke@huawei.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).