From: Jason Wang <jasowang@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, wangyunjian <wangyunjian@huawei.com>
Cc: caihe@huawei.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH v2] tap: fix memory leak on success to create a tap device
Date: Thu, 19 Jul 2018 16:53:52 +0800 [thread overview]
Message-ID: <6cde2d66-29cc-e8d4-c038-f494f093e7de@redhat.com> (raw)
In-Reply-To: <153193157775.25234.15329587771745338735@sif>
On 2018年07月19日 00:32, Michael Roth wrote:
> Quoting Jason Wang (2018-05-31 04:46:05)
>> On 2018年05月31日 15:28, wangyunjian wrote:
>>> From: Yunjian Wang<wangyunjian@huawei.com>
>>>
>>> The memory leak on success to create a tap device. And the nfds and
>>> nvhosts may not be the same and need to be processed separately.
>>>
>>> Fixes: 07825977 ("tap: fix memory leak on failure to create a multiqueue tap device")
>>> Fixes: 264986e2 ("tap: multiqueue support")
>>>
>>> CC: QEMU Stable<qemu-stable@nongnu.org>
>>> Signed-off-by: Yunjian Wang<wangyunjian@huawei.com>
>>> ---
>>> v2:
>>> -add commit log and cc qemu-stable with fixes tags
>>> ---
>> Applied.
> It looks like this hasn't made its way to master yet. Is a pull request
> still planned?
>
Fall through cracks unfortuately. It will be included in the next pull
request.
Thanks
prev parent reply other threads:[~2018-07-19 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 7:28 [Qemu-devel] [PATCH v2] tap: fix memory leak on success to create a tap device wangyunjian
2018-05-31 9:46 ` Jason Wang
2018-07-18 16:32 ` [Qemu-devel] [Qemu-stable] " Michael Roth
2018-07-19 8:53 ` Jason Wang [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=6cde2d66-29cc-e8d4-c038-f494f093e7de@redhat.com \
--to=jasowang@redhat.com \
--cc=caihe@huawei.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=wangyunjian@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).