All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: jingjing.wu@intel.com, dev@dpdk.org
Subject: Re: [PATCH v2] app/testpmd: fix memory leak
Date: Mon, 30 Jan 2017 10:33:18 +0100	[thread overview]
Message-ID: <20170130093318.GB10133@6wind.com> (raw)
In-Reply-To: <1485528898-53283-1-git-send-email-pablo.de.lara.guarch@intel.com>

Hi Pablo,

On Fri, Jan 27, 2017 at 02:54:58PM +0000, Pablo de Lara wrote:
> Free memory when port flow entry creation fails.
> 
> Coverity issue: 139600
> Fixes: 938a184a1870 ("app/testpmd: implement basic support for flow API")
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> Changes in v2:
> 
> - Removed unnecessary conditional
> 
>  app/test-pmd/config.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
> index 5834498..467932f 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -954,6 +954,7 @@ port_flow_new(const struct rte_flow_attr *attr,
>  		goto store;
>  	}
>  notsup:
> +	free(pf);
>  	rte_errno = err;
>  	return NULL;
>  }
> -- 
> 2.7.4
> 

I think this is a false positive, which is why I did not address it during
the last round of Coverity issues.

As a two-pass function, errors are checked during the first pass, when pf is
not allocated yet. During the second pass, intermediate functions are not
supposed to return a different result and "notsup" cannot occur.

I think assert()/rte_assert() would make more sense and should fool Coverity
into understanding the expected behavior.

The commit log should reflect that we are addressing a false positive since
there is no problem with the code logic (of course unless I missed anything
obvious).

Thanks.

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2017-01-30  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 13:15 [PATCH] app/testpmd: fix memory leak Pablo de Lara
2017-01-27 14:54 ` [PATCH v2] " Pablo de Lara
2017-01-30  9:33   ` Adrien Mazarguil [this message]
2017-01-30 12:26     ` De Lara Guarch, Pablo

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=20170130093318.GB10133@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=pablo.de.lara.guarch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.