From: Max Reitz <mreitz@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Jason Dillaman <dillaman@redhat.com>,
Florian Florensa <fflorensa@online.net>,
Peter Lieven <pl@kamp.de>,
qemu-block@nongnu.org
Subject: Re: [PATCH 0/2] block/rbd: fix memory leaks
Date: Tue, 6 Apr 2021 19:06:35 +0200 [thread overview]
Message-ID: <b6c205ab-356a-ed3c-0442-105668db19d9@redhat.com> (raw)
In-Reply-To: <20210329150129.121182-1-sgarzare@redhat.com>
On 29.03.21 17:01, Stefano Garzarella wrote:
> This series fixes two memory leaks, found through valgrind, in the
> rbd driver.
>
> Stefano Garzarella (2):
> block/rbd: fix memory leak in qemu_rbd_connect()
> block/rbd: fix memory leak in qemu_rbd_co_create_opts()
>
> block/rbd.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
I’m not quite sure whether this is fit for 6.0... I think it’s too late
for rc2, so I don’t know.
Max
next prev parent reply other threads:[~2021-04-06 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 15:01 [PATCH 0/2] block/rbd: fix memory leaks Stefano Garzarella
2021-03-29 15:01 ` [PATCH 1/2] block/rbd: fix memory leak in qemu_rbd_connect() Stefano Garzarella
2021-04-06 8:22 ` Markus Armbruster
2021-04-08 7:49 ` Stefano Garzarella
2021-03-29 15:01 ` [PATCH 2/2] block/rbd: fix memory leak in qemu_rbd_co_create_opts() Stefano Garzarella
2021-04-06 8:23 ` Markus Armbruster
2021-04-06 17:06 ` Max Reitz [this message]
2021-04-07 9:38 ` [PATCH 0/2] block/rbd: fix memory leaks Markus Armbruster
2021-04-08 7:54 ` Stefano Garzarella
2021-04-07 13:31 ` 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=b6c205ab-356a-ed3c-0442-105668db19d9@redhat.com \
--to=mreitz@redhat.com \
--cc=dillaman@redhat.com \
--cc=fflorensa@online.net \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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).