From: Kevin Traynor <ktraynor@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Itsuro Oda <oda@valinux.co.jp>,
tiwei.bie@intel.com, zhihong.wang@intel.com,
anatoly.burakov@intel.com, dev@dpdk.org, stable@dpdk.org
Cc: Xiaolong Ye <xiaolong.ye@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/vhost: fix potential memory leak
Date: Fri, 20 Mar 2020 19:25:04 +0000 [thread overview]
Message-ID: <89a6e278-1fda-0b6d-2df4-4b56ae022f40@redhat.com> (raw)
In-Reply-To: <0a169c6f-7f63-7df0-852a-fff4ddadcfc6@redhat.com>
On 20/03/2020 16:23, Maxime Coquelin wrote:
>
>
> On 3/19/20 6:15 PM, Kevin Traynor wrote:
>> Hi Itsuro,
>>
>> On 05/03/2020 02:54, Itsuro Oda wrote:
>>> If a vhost device is closed before eth_dev_configure is done
>>> to the device, internal resources allocated to the device
>>> would not be freed. This patch fixes it.
>>>
>>> Fixes: 3d01b759d267 ("net/vhost: delay driver setup")
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Itsuro Oda <oda@valinux.co.jp>
>>> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
>>
>> This fixes an issue with the patch you backported for 18.11. Is the
>> issue also present in the backported version?
>>
>> If so, this patch is not in upstream dpdk or gone through validation. So
>> the choices are,
>>
>> 1. revert your patches from 18.11
>> 2. go ahead on stable without this patch
>> 3. delay until this patch is in master (but not until validated) and
>> then backport to stable
>>
>> Itsuro/Maxime, what do you think?
>
> I think you should drop Itsuro patches for now, as long as this patch is
> not in master. Secondary process was broken for several revisions in
> Vhost, so it is better to keep it broken for now than risking
> regressions on primary process support.
>
I agree, vhost primary is too well used to take risks on regression
while there are still some outstanding issues being resolved with these
patches for secondary process.
Patches reverted.
> If this patch is in master before the next 18.11 is done, then we can
> pick all the patches.
>
Yes, we can do that.
thanks,
Kevin.
> Thanks,
> Maxime
>> thanks,
>> Kevin.
>>
>>> ---
>>> v2:
>>> - fix commit message
>>>
>>> v3:
>>> - fix spell error of Reviewed-by
>>>
>>> drivers/net/vhost/rte_eth_vhost.c | 16 +++++++---------
>>> 1 file changed, 7 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/drivers/net/vhost/rte_eth_vhost.c b/drivers/net/vhost/rte_eth_vhost.c
>>> index 458ed58f5..1ed977e9b 100644
>>> --- a/drivers/net/vhost/rte_eth_vhost.c
>>> +++ b/drivers/net/vhost/rte_eth_vhost.c
>>> @@ -1065,16 +1065,14 @@ eth_dev_close(struct rte_eth_dev *dev)
>>>
>>> eth_dev_stop(dev);
>>>
>>> - rte_vhost_driver_unregister(internal->iface_name);
>>> -
>>> list = find_internal_resource(internal->iface_name);
>>> - if (!list)
>>> - return;
>>> -
>>> - pthread_mutex_lock(&internal_list_lock);
>>> - TAILQ_REMOVE(&internal_list, list, next);
>>> - pthread_mutex_unlock(&internal_list_lock);
>>> - rte_free(list);
>>> + if (list) {
>>> + rte_vhost_driver_unregister(internal->iface_name);
>>> + pthread_mutex_lock(&internal_list_lock);
>>> + TAILQ_REMOVE(&internal_list, list, next);
>>> + pthread_mutex_unlock(&internal_list_lock);
>>> + rte_free(list);
>>> + }
>>>
>>> if (dev->data->rx_queues)
>>> for (i = 0; i < dev->data->nb_rx_queues; i++)
>>>
>>
next prev parent reply other threads:[~2020-03-20 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 0:03 [dpdk-dev] [PATCH] " Itsuro Oda
2020-03-05 2:15 ` Ye Xiaolong
2020-03-05 2:50 ` [dpdk-dev] [PATCH v2] " Itsuro Oda
2020-03-05 2:54 ` [dpdk-dev] [PATCH v3] " Itsuro Oda
2020-03-19 17:15 ` Kevin Traynor
2020-03-20 16:23 ` Maxime Coquelin
2020-03-20 19:25 ` Kevin Traynor [this message]
2020-04-10 14:44 ` Maxime Coquelin
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=89a6e278-1fda-0b6d-2df4-4b56ae022f40@redhat.com \
--to=ktraynor@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=oda@valinux.co.jp \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@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).