From: Thomas Monjalon <thomas@monjalon.net>
To: byron.marohn@intel.com
Cc: dev@dpdk.org, Hari Kumar Vemula <hari.kumarx.vemula@intel.com>,
reshma.pattan@intel.com, pablo.de.lara.guarch@intel.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] lib/efd: fix to free tail queue entry after use
Date: Sun, 18 Nov 2018 15:57:07 +0100 [thread overview]
Message-ID: <1638966.uzRZUHLhb0@xps> (raw)
In-Reply-To: <1542194265-16156-1-git-send-email-hari.kumarx.vemula@intel.com>
This patch is not trivial, it may require an ack from a maintainer,
Pablo is unavailable this month.
Byron, any comment please?
14/11/2018 12:17, Hari Kumar Vemula:
> In rte_efd_create() allocated memory for tail queue entry but
> not freed.
> Added freeing the tail queue entry.
>
> Fixes: 56b6ef874f80 ("efd: new Elastic Flow Distributor library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hari Kumar Vemula <hari.kumarx.vemula@intel.com>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2018-11-18 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 11:45 [dpdk-stable] [PATCH] lib: fix to free trail " Hari Kumar Vemula
2018-11-13 16:43 ` Pattan, Reshma
2018-11-14 11:17 ` [dpdk-stable] [PATCH v2] lib/efd: fix to free tail " Hari Kumar Vemula
2018-11-18 14:57 ` Thomas Monjalon [this message]
2018-11-23 13:30 ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin
2018-11-23 14:39 ` Maxime Coquelin
2019-01-11 11:49 ` [dpdk-stable] [PATCH v3] " Hari Kumar Vemula
2019-01-14 22:30 ` Thomas Monjalon
2019-01-14 22:39 ` [dpdk-stable] [dpdk-dev] " Honnappa Nagarahalli
2019-01-17 13:36 ` [dpdk-stable] [PATCH v4] " Hari Kumar Vemula
2019-01-17 16:41 ` De Lara Guarch, Pablo
2019-01-18 7:40 ` [dpdk-stable] [PATCH v5] " Hari Kumar Vemula
2019-01-18 18:21 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=1638966.uzRZUHLhb0@xps \
--to=thomas@monjalon.net \
--cc=byron.marohn@intel.com \
--cc=dev@dpdk.org \
--cc=hari.kumarx.vemula@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=reshma.pattan@intel.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).