From: Jeff Guo <jia.guo@intel.com>
To: wangyunjian <wangyunjian@huawei.com>, dev@dpdk.org
Cc: jerry.lilijun@huawei.com, xudingke@huawei.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal: fix memory leak when removing event_cb
Date: Thu, 2 Jul 2020 17:28:14 +0800 [thread overview]
Message-ID: <2706952f-9788-b597-cf68-78f4dd3ed96d@intel.com> (raw)
In-Reply-To: <1593518201-27524-1-git-send-email-wangyunjian@huawei.com>
hi, yunjian
On 6/30/2020 7:56 PM, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> The event_cb->dev_name is not freed when freeing event_cb,
> and this causes a memory leak.
>
> Fixes: a753e53d517b ("eal: add device event monitor framework")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
> lib/librte_eal/common/eal_common_dev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/librte_eal/common/eal_common_dev.c b/lib/librte_eal/common/eal_common_dev.c
> index 9e4f09d..4cfdb80 100644
> --- a/lib/librte_eal/common/eal_common_dev.c
> +++ b/lib/librte_eal/common/eal_common_dev.c
> @@ -526,6 +526,8 @@ static int cmp_dev_name(const struct rte_device *dev, const void *_name)
> */
> if (event_cb->active == 0) {
> TAILQ_REMOVE(&dev_event_cbs, event_cb, next);
> + if (event_cb->dev_name)
> + free(event_cb->dev_name);
> free(event_cb);
> ret++;
> } else {
Could you please to check is there another part need to check memory
leak like that, such as in rte_dev_event_callback_register?
next prev parent reply other threads:[~2020-07-02 9:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:33 [dpdk-dev] [PATCH 0/3] fixes for device event wangyunjian
2020-06-03 12:54 ` wangyunjian
2020-06-03 12:54 ` [dpdk-dev] [PATCH 1/3] eal: fix memory leak when removing event_cb wangyunjian
2020-06-03 12:55 ` [dpdk-dev] [PATCH 2/3] eal: fix remove incorrect event_cb wangyunjian
2020-06-12 5:56 ` Jeff Guo
2020-06-30 11:29 ` wangyunjian
2020-06-30 11:56 ` [dpdk-dev] [PATCH v2] eal: fix memory leak when removing event_cb wangyunjian
2020-07-02 9:28 ` Jeff Guo [this message]
2020-07-02 10:53 ` wangyunjian
2020-07-02 11:46 ` [dpdk-dev] [PATCH v3 0/2] fixes for device event wangyunjian
2020-07-02 11:47 ` [dpdk-dev] [PATCH v3 1/2] eal: fix memory leak when removing event_cb wangyunjian
2020-07-03 6:04 ` Jeff Guo
2020-07-03 7:00 ` wangyunjian
2020-07-03 7:23 ` [dpdk-dev] [dpdk-stable] " David Marchand
2020-07-03 7:52 ` wangyunjian
2020-07-03 8:01 ` David Marchand
2020-07-02 11:47 ` [dpdk-dev] [PATCH v3 2/2] eal: return error code when failure wangyunjian
2020-06-03 12:55 ` [dpdk-dev] [PATCH 3/3] " wangyunjian
2020-07-02 9:18 ` Jeff Guo
2020-07-02 10:43 ` wangyunjian
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=2706952f-9788-b597-cf68-78f4dd3ed96d@intel.com \
--to=jia.guo@intel.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--cc=xudingke@huawei.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).