From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>, dev@dpdk.org
Cc: cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] net/softnic: fix resource leak for pipeline
Date: Fri, 1 May 2020 16:48:38 +0100 [thread overview]
Message-ID: <b0f97dbf-333a-2e86-9333-eee03b77f10d@intel.com> (raw)
In-Reply-To: <20200427171551.82235-1-jasvinder.singh@intel.com>
On 4/27/2020 6:15 PM, Jasvinder Singh wrote:
> For sending request messages to data plane threads, the
> caller invokes pipeline_msg_send_recv() function which never
> returns null response. Thus, removed redundant check on
> the returned response.
>
> Coverity Issues: 357676, 357680, 357681, 357682, 357690, 357693, 357711,
> 357722, 357725, 357734, 357739, 357743, 357747,357762, 357766, 357787
>
> Fixes: 6d4d05402501 ("net/softnic: add command to read stats")
> Fixes: 202905f3ee4d ("net/softnic: add command to create objects")
> Fixes: ee19326a4b1e ("net/softnic: add command for pipeline table entries")
> Fixes: 9bc0ce0ad17c ("net/softnic: add command for meter action")
> Fixes: 2505030a8383 ("net/softnic: add command for TTL action")
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2020-05-01 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 14:03 [dpdk-dev] [PATCH] net/softnic: fix resource leak Jasvinder Singh
2020-04-27 17:15 ` [dpdk-dev] [PATCH v2] net/softnic: fix resource leak for pipeline Jasvinder Singh
2020-05-01 15:48 ` Ferruh Yigit [this message]
2020-05-13 12:45 ` [dpdk-dev] [PATCH] net/softnic: fix resource leak Mcnamara, John
2020-05-13 13:55 ` Dumitrescu, Cristian
2020-05-13 15:32 ` Ferruh Yigit
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=b0f97dbf-333a-2e86-9333-eee03b77f10d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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 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).