From: David Marchand <david.marchand@redhat.com>
To: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Cc: dev <dev@dpdk.org>, "Pattan, Reshma" <reshma.pattan@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>,
"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] bus/fslmc: fix for resource leak coverity issue
Date: Thu, 31 Oct 2019 17:18:24 +0100 [thread overview]
Message-ID: <CAJFAV8x_zPRUEeCXjKjdn7MuG2P7SXiKCBB43zrPZaWTpFV5cQ@mail.gmail.com> (raw)
In-Reply-To: <1568100655-20010-1-git-send-email-agalyax.babu.radhakrishnan@intel.com>
On Tue, Sep 10, 2019 at 9:33 AM Agalya Babu RadhaKrishnan
<agalyax.babu.radhakrishnan@intel.com> wrote:
>
> From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
>
> 1 issue caught by 344967
> Leaked_storage: Variable sep going out of scope leaks the
> storage it points to.
>
> When 'sep' is not null and sep_exist is 0, 'sep' is freed
> before going out of scope of the function irrespective of
> 'addr' exists or not.
>
> Coverity Issue: 344967
s/Issue/issue/ according to the contributing guide.
> Fixes: e67a61614d0b ("bus/fslmc: support device iteration")
> Cc: stable@dpdk.org
>
> Signed-off-by: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Acked-by: Sachin Saxena <sachin.saxena@nxp.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2019-10-31 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 7:30 [dpdk-stable] " Agalya Babu RadhaKrishnan
2019-09-10 7:41 ` Babu Radhakrishnan, AgalyaX
2019-10-03 8:43 ` Sachin Saxena
2019-10-24 19:17 ` [dpdk-stable] [dpdk-dev] " David Marchand
2019-10-31 11:16 ` Sachin Saxena
2019-10-03 8:40 ` [dpdk-stable] " Sachin Saxena
2019-10-31 16:18 ` David Marchand [this message]
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=CAJFAV8x_zPRUEeCXjKjdn7MuG2P7SXiKCBB43zrPZaWTpFV5cQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=agalyax.babu.radhakrishnan@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=reshma.pattan@intel.com \
--cc=sachin.saxena@nxp.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).