From: Keith Busch <keith.busch@intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Keith Busch <keith.busch@intel.com>,
Lu Lina <lina.lulina@huawei.com>,
qemu-devel@nongnu.org, Ting Wang <kathy.wangting@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] nvme: Fix memleak in nvme_dma_read_prp
Date: Fri, 19 Jun 2015 14:54:16 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1506191453110.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <20150619125727.GB18007@stefanha-thinkpad.redhat.com>
On Fri, 19 Jun 2015, Stefan Hajnoczi wrote:
>> From: Lu Lina <lina.lulina@huawei.com>
>>
>> Signed-off-by: Lu Lina <lina.lulina@huawei.com>
Thanks for the fix.
Acked-by: Keith Busch <keith.busch@intel.com>
>> @@ -154,6 +154,7 @@ static uint16_t nvme_dma_read_prp(NvmeCtrl *n, uint8_t *ptr, uint32_t len,
>> qemu_sglist_destroy(&qsg);
>> return NVME_INVALID_FIELD | NVME_DNR;
>> }
>> + qemu_sglist_destroy(&qsg);
>> return NVME_SUCCESS;
>> }
next prev parent reply other threads:[~2015-06-19 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 6:27 [Qemu-devel] [PATCH] nvme: Fix memleak in nvme_dma_read_prp Ting Wang
2015-06-19 12:57 ` Stefan Hajnoczi
2015-06-19 14:54 ` Keith Busch [this message]
2015-06-22 9:58 ` Stefan Hajnoczi
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=alpine.LNX.2.00.1506191453110.15930@localhost.lm.intel.com \
--to=keith.busch@intel.com \
--cc=kathy.wangting@huawei.com \
--cc=lina.lulina@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.