From: wangyunjian <wangyunjian@huawei.com>
To: David Marchand <david.marchand@redhat.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>, Sachin Saxena <sachin.saxena@nxp.com>,
"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
xudingke <xudingke@huawei.com>, "dpdk stable" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/1] bus/fslmc: fix memory leak in secondary process
Date: Fri, 17 Jul 2020 09:36:59 +0000 [thread overview]
Message-ID: <34EFBCA9F01B0748BEB6B629CE643AE60D0D62C7@DGGEMM533-MBX.china.huawei.com> (raw)
In-Reply-To: <CAJFAV8zy-POV_Hs1qk+Wb=Yn0i76ma+7YaBiJc1J_q0r=5KKTQ@mail.gmail.com>
> -----Original Message-----
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Friday, July 17, 2020 5:21 PM
> To: wangyunjian <wangyunjian@huawei.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>
> Cc: dev <dev@dpdk.org>; Sachin Saxena <sachin.saxena@nxp.com>; Lilijun
> (Jerry) <jerry.lilijun@huawei.com>; xudingke <xudingke@huawei.com>; dpdk
> stable <stable@dpdk.org>
> Subject: Re: [dpdk-dev] [PATCH 1/1] bus/fslmc: fix memory leak in secondary
> process
>
> On Thu, Jul 9, 2020 at 12:40 PM wangyunjian <wangyunjian@huawei.com>
> wrote:
> >
> > From: Yunjian Wang <wangyunjian@huawei.com>
> >
> > In fslmc_process_mcp(), we allocate memory for 'dev_name' but not
> > released before return in secondary process.
>
> dev_name is not used anymore since a69f79300262 ("bus/fslmc: support multi
> VFIO group") We can remove it entirely in this function.
Thanks for your suggestion, will include it in next version.
Yunjian
>
> --
> David Marchand
next prev parent reply other threads:[~2020-07-17 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 10:39 wangyunjian
2020-07-09 15:15 ` Hemant Agrawal
2020-07-17 9:20 ` David Marchand
2020-07-17 9:36 ` wangyunjian [this message]
2020-07-17 10:50 ` [dpdk-dev] [PATCH v2] " wangyunjian
2020-07-20 5:28 ` Hemant Agrawal (OSS)
2020-07-21 18:52 ` David Marchand
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=34EFBCA9F01B0748BEB6B629CE643AE60D0D62C7@DGGEMM533-MBX.china.huawei.com \
--to=wangyunjian@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerry.lilijun@huawei.com \
--cc=sachin.saxena@nxp.com \
--cc=stable@dpdk.org \
--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).