From: Gagandeep Singh <G.Singh@nxp.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/pfe: do not use a possibly NULL Pointer
Date: Mon, 24 May 2021 09:25:28 +0000 [thread overview]
Message-ID: <VI1PR04MB6960AC3C1899B56EA9BD5B0EE1269@VI1PR04MB6960.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210524085917.16254-1-thierry.herbelot@6wind.com>
> -----Original Message-----
> From: Thierry Herbelot <thierry.herbelot@6wind.com>
> Sent: Monday, May 24, 2021 2:29 PM
> To: dev@dpdk.org
> Cc: Thierry Herbelot <thierry.herbelot@6wind.com>; Thomas Monjalon
> <thomas@monjalon.net>; stable@dpdk.org; Gagandeep Singh
> <G.Singh@nxp.com>
> Subject: [PATCH] net/pfe: do not use a possibly NULL Pointer
>
> Use dev only after it was checked not to be NULL.
>
> Fixes: acd4818ea2a45 ("net/pfe: add link status update")
> Cc: stable@dpdk.org
> Cc: Gagandeep Singh <g.singh@nxp.com>
>
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> ---
> drivers/net/pfe/pfe_ethdev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/pfe/pfe_ethdev.c b/drivers/net/pfe/pfe_ethdev.c
> index 3135466713fb..09048e57d973 100644
> --- a/drivers/net/pfe/pfe_ethdev.c
> +++ b/drivers/net/pfe/pfe_ethdev.c
> @@ -578,7 +578,7 @@ static int
> pfe_eth_link_update(struct rte_eth_dev *dev, int wait_to_complete
> __rte_unused)
> {
> int ret, ioctl_cmd = 0;
> - struct pfe_eth_priv_s *priv = dev->data->dev_private;
> + struct pfe_eth_priv_s *priv;
> struct rte_eth_link link, old;
> unsigned int lstatus = 1;
>
> @@ -586,6 +586,7 @@ pfe_eth_link_update(struct rte_eth_dev *dev, int
> wait_to_complete __rte_unused)
> PFE_PMD_ERR("Invalid device in link_update.\n");
> return 0;
> }
> + priv = dev->data->dev_private;
"dev" will never be NULL here because librte_ethdev library is already doing some checks on dev before calling the link update. So please remove the if check.
>
> memset(&old, 0, sizeof(old));
> memset(&link, 0, sizeof(struct rte_eth_link));
> --
> 2.29.2
next prev parent reply other threads:[~2021-05-24 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 8:59 Thierry Herbelot
2021-05-24 9:25 ` Gagandeep Singh [this message]
2021-05-24 9:37 ` [dpdk-dev] [PATCH v2] net/pfe: no need to check dev to be " Thierry Herbelot
2021-05-24 10:28 ` Gagandeep Singh
2021-06-29 8:27 ` Andrew Rybchenko
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=VI1PR04MB6960AC3C1899B56EA9BD5B0EE1269@VI1PR04MB6960.eurprd04.prod.outlook.com \
--to=g.singh@nxp.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--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 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).