From: Markus Armbruster <armbru@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Florian Florensa <fflorensa@online.net>,
Jason Dillaman <dillaman@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH 0/2] block/rbd: fix memory leaks
Date: Wed, 07 Apr 2021 11:38:17 +0200 [thread overview]
Message-ID: <87y2duzb7a.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <b6c205ab-356a-ed3c-0442-105668db19d9@redhat.com> (Max Reitz's message of "Tue, 6 Apr 2021 19:06:35 +0200")
Max Reitz <mreitz@redhat.com> writes:
> 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.
This the maintainers' call to make.
* PATCH 1:
CON: Old bug, probably 2.9, i.e. four years
PRO: The fix is straightforward
* PATCH 2:
NEUTRAL: Not recent from upstream's point of view (5.0), but
downstreams may have different ideas
PRO: The fix is trivial
I encourage you to take at least PATCH 2.
next prev parent reply other threads:[~2021-04-07 9:39 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 ` [PATCH 0/2] block/rbd: fix memory leaks Max Reitz
2021-04-07 9:38 ` Markus Armbruster [this message]
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=87y2duzb7a.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dillaman@redhat.com \
--cc=fflorensa@online.net \
--cc=kwolf@redhat.com \
--cc=mreitz@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 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.