From: Gagandeep Singh <G.Singh@nxp.com>
To: "Hemant Agrawal (OSS)" <hemant.agrawal@oss.nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>
Cc: Vanshika Shukla <vanshika.shukla@nxp.com>
Subject: RE: [PATCH v2 5/5] net/dpaa: Fix coverity issue
Date: Mon, 13 Oct 2025 07:08:38 +0000 [thread overview]
Message-ID: <AS8PR04MB81987B4C79A51D99A35A00DFE1EAA@AS8PR04MB8198.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <87aaf909-e17c-47c7-a83e-acf61d2fdb03@oss.nxp.com>
Hi
> -----Original Message-----
> From: Hemant Agrawal (OSS) <hemant.agrawal@oss.nxp.com>
> Sent: Thursday, October 9, 2025 3:19 PM
> To: Gagandeep Singh <G.Singh@nxp.com>; dev@dpdk.org; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Sachin Saxena <sachin.saxena@nxp.com>
> Cc: Vanshika Shukla <vanshika.shukla@nxp.com>
> Subject: Re: [PATCH v2 5/5] net/dpaa: Fix coverity issue
>
>
> On 08-10-2025 10:05, Gagandeep Singh wrote:
> > From: Vanshika Shukla <vanshika.shukla@nxp.com>
> >
> > Fix Resource leak CID:362787 issue reported by external coverity tool.
>
> This is internal NXP coverity issue? can you also add details about the issue here?
>
No, This issue is reported by DPDK Coverity scan tool: https://scan4.scan.coverity.com/#/project-view/68868/10075?selectedIssue=362787
I will add more details in commit.
>
> >
> > Signed-off-by: Vanshika Shukla <vanshika.shukla@nxp.com>
> > ---
> > drivers/net/dpaa/dpaa_flow.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/dpaa/dpaa_flow.c b/drivers/net/dpaa/dpaa_flow.c
> > index 2a22b23c8f..417b9b6fbb 100644
> > --- a/drivers/net/dpaa/dpaa_flow.c
> > +++ b/drivers/net/dpaa/dpaa_flow.c
> > @@ -1,5 +1,5 @@
> > /* SPDX-License-Identifier: BSD-3-Clause
> > - * Copyright 2017-2019,2021-2024 NXP
> > + * Copyright 2017-2019,2021-2025 NXP
> > */
> >
> > /* System headers */
> > @@ -889,9 +889,9 @@ int dpaa_fm_init(void)
> > /* FM PCD Enable */
> > ret = fm_pcd_enable(pcd_handle);
> > if (ret) {
> > - fm_close(fman_handle);
> > - fm_pcd_close(pcd_handle);
> > DPAA_PMD_ERR("fm_pcd_enable: Failed");
> > + fm_pcd_close(pcd_handle);
> > + fm_close(fman_handle);
> > return -1;
> > }
> >
next prev parent reply other threads:[~2025-10-13 7:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 5:00 [PATCH 0/5] DPAA specific changes Gagandeep Singh
2025-10-07 5:00 ` [PATCH 1/5] bus/dpaa: add FQ shutdown and improve logging Gagandeep Singh
2025-10-07 5:00 ` [PATCH 2/5] net/dpaa: Support IEEE1588 by timesync API Gagandeep Singh
2025-10-07 5:00 ` [PATCH 3/5] bus/dpaa: Disable qman Invalid Enqueue State interrupt Gagandeep Singh
2025-10-07 5:00 ` [PATCH 4/5] bus/dpaa: Set max push RXQ number Gagandeep Singh
2025-10-07 5:00 ` [PATCH 5/5] net/dpaa: Fix coverity issue Gagandeep Singh
2025-10-08 4:35 ` [PATCH v2 0/5] DPAA specific changes Gagandeep Singh
2025-10-08 4:35 ` [PATCH v2 1/5] bus/dpaa: add FQ shutdown and improve logging Gagandeep Singh
2025-10-09 9:44 ` Hemant Agrawal
2025-10-08 4:35 ` [PATCH v2 2/5] net/dpaa: Support IEEE1588 by timesync API Gagandeep Singh
2025-10-08 4:35 ` [PATCH v2 3/5] bus/dpaa: Disable qman Invalid Enqueue State interrupt Gagandeep Singh
2025-10-08 4:35 ` [PATCH v2 4/5] bus/dpaa: Set max push RXQ number Gagandeep Singh
2025-10-08 4:35 ` [PATCH v2 5/5] net/dpaa: Fix coverity issue Gagandeep Singh
2025-10-09 9:49 ` Hemant Agrawal
2025-10-13 7:08 ` Gagandeep Singh [this message]
2025-10-14 10:17 ` [PATCH v3 0/5] DPAA specific changes Gagandeep Singh
2025-10-14 10:17 ` [PATCH v3 1/5] bus/dpaa: add FQ shutdown and improve logging Gagandeep Singh
2025-10-15 15:32 ` Hemant Agrawal
2025-10-14 10:17 ` [PATCH v3 2/5] net/dpaa: Support IEEE1588 by timesync API Gagandeep Singh
2025-10-14 10:17 ` [PATCH v3 3/5] bus/dpaa: Disable qman Invalid Enqueue State interrupt Gagandeep Singh
2025-10-14 10:17 ` [PATCH v3 4/5] bus/dpaa: Set max push RXQ number Gagandeep Singh
2025-10-14 10:17 ` [PATCH v3 5/5] net/dpaa: fix resource leak coverity issue Gagandeep Singh
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=AS8PR04MB81987B4C79A51D99A35A00DFE1EAA@AS8PR04MB8198.eurprd04.prod.outlook.com \
--to=g.singh@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hemant.agrawal@oss.nxp.com \
--cc=sachin.saxena@nxp.com \
--cc=vanshika.shukla@nxp.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).