From: Jerin Jacob <jerinjacobk@gmail.com>
To: wangyunjian <wangyunjian@huawei.com>
Cc: dpdk-dev <dev@dpdk.org>, Hemant Agrawal <hemant.agrawal@nxp.com>,
Nipun Gupta <nipun.gupta@nxp.com>,
"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
xudingke <xudingke@huawei.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] event/dpaa2: fix dereference before null check
Date: Sun, 4 Oct 2020 16:11:46 +0530 [thread overview]
Message-ID: <CALBAE1MQA1a5L1=UfSqRfx5go0u_jnar2+BP-0CuqRgQU5weUQ@mail.gmail.com> (raw)
In-Reply-To: <befbb8824171ccb7493fc968ee732263fbc32f52.1598423164.git.wangyunjian@huawei.com>
On Wed, Aug 26, 2020 at 6:37 PM wangyunjian <wangyunjian@huawei.com> wrote:
>
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> Coverity flags that 'portal' variable is used before
> it's checked for NULL. This patch fixes this issue.
>
> Coverity issue: 323516
> Fixes: 4ab57b042e7c ("event/dpaa2: affine portal at runtime during I/O")
> Cc: stable@dpdk.org
dpaa2 maintainers, Please review this.
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
> drivers/event/dpaa2/dpaa2_eventdev.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/event/dpaa2/dpaa2_eventdev.c b/drivers/event/dpaa2/dpaa2_eventdev.c
> index 3ae4441ee..f7383ca73 100644
> --- a/drivers/event/dpaa2/dpaa2_eventdev.c
> +++ b/drivers/event/dpaa2/dpaa2_eventdev.c
> @@ -569,14 +569,14 @@ dpaa2_eventdev_port_release(void *port)
>
> EVENTDEV_INIT_FUNC_TRACE();
>
> + if (portal == NULL)
> + return;
> +
> /* TODO: Cleanup is required when ports are in linked state. */
> if (portal->is_port_linked)
> DPAA2_EVENTDEV_WARN("Event port must be unlinked before release");
>
> - if (portal)
> - rte_free(portal);
> -
> - portal = NULL;
> + rte_free(portal);
> }
>
> static int
> --
> 2.23.0
>
>
next prev parent reply other threads:[~2020-10-04 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 13:07 wangyunjian
2020-10-04 10:41 ` Jerin Jacob [this message]
2020-10-04 10:53 ` Nipun Gupta
2020-10-05 9:40 ` Jerin Jacob
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='CALBAE1MQA1a5L1=UfSqRfx5go0u_jnar2+BP-0CuqRgQU5weUQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerry.lilijun@huawei.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--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).