From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: fix resource leak for pipeline
Date: Sun, 24 May 2020 18:18:55 +0200 [thread overview]
Message-ID: <3421280.ccbjClniuP@thomas> (raw)
In-Reply-To: <20200427165700.50643-1-jasvinder.singh@intel.com>
27/04/2020 18:57, Jasvinder Singh:
> 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: 357750, 357740, 357749, 357758, 357702, 357736,
> 357679, 357791, 357738, 357778, 357716, 357705, 357776, 357753,
> 357729, 357735
>
> Fixes: 50e73d051806 ("examples/ip_pipeline: add stats read commands")
> Fixes: 6b1b3c3c9d30 ("examples/ip_pipeline: add port enable and disable commands")
> Fixes: a3a95b7d58b9 ("examples/ip_pipeline: add table entry commands")
> Fixes: 3186282f8e12 ("examples/ip_pipeline: add table bulk add command")
> Fixes: f634e4c5698a ("examples/ip_pipeline: add table entry delete command")
> Fixes: c64b9121a963 ("examples/ip_pipeline: add table entry stats command")
> Fixes: 7e11393e40ef ("examples/ip_pipeline: add meter profile commands")
> Fixes: e92058d604e6 ("examples/ip_pipeline: add meter stats command")
> Fixes: 2b82ef4861c0 ("examples/ip_pipeline: add DSCP table update command")
> Fixes: d0d306c7f2a1 ("examples/ip_pipeline: add TTL stats command")
> Fixes: a3169ee5ec59 ("examples/ip_pipeline: support rule time read")
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
This patch has been forgotten.
Applied and squashed with "fix resource leak for thread".
prev parent reply other threads:[~2020-05-24 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 16:57 Jasvinder Singh
2020-05-24 16:18 ` Thomas Monjalon [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=3421280.ccbjClniuP@thomas \
--to=thomas@monjalon.net \
--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).