From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-io: Fix memory leak
Date: Wed, 8 Jul 2009 16:11:31 +0200 [thread overview]
Message-ID: <20090708141131.GA26000@lst.de> (raw)
In-Reply-To: <1247055695-4533-1-git-send-email-kwolf@redhat.com>
On Wed, Jul 08, 2009 at 02:21:35PM +0200, Kevin Wolf wrote:
> qemu-io leaks the request buffer whenever the read or write function isn't
> executed completely down the "normal" code path.
Looks good. The same problems also happens in the vectored and aio
read/write command, I'll cook up a patch to fix those.
next prev parent reply other threads:[~2009-07-08 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 12:21 [Qemu-devel] [PATCH] qemu-io: Fix memory leak Kevin Wolf
2009-07-08 14:11 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-18 9:42 Kevin Wolf
2009-11-18 19:04 ` Christoph Hellwig
2009-11-20 8:05 ` Amit Shah
2009-11-20 8:35 ` Kevin Wolf
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=20090708141131.GA26000@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).