From: Maxim Levitsky <mlevitsk@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v2 1/2] crypto: luks: fix tiny memory leak
Date: Tue, 13 Oct 2020 15:31:42 +0300 [thread overview]
Message-ID: <96c95d7b4aef3dd0cb2e832c1f0c012f40a8da56.camel@redhat.com> (raw)
In-Reply-To: <w51eem2z4zd.fsf@maestria.local.igalia.com>
On Tue, 2020-10-13 at 14:26 +0200, Alberto Garcia wrote:
> On Sun 11 Oct 2020 12:21:35 PM CEST, Maxim Levitsky wrote:
> > In the case when underlying block device doesn't support the
> > bdrv_co_delete_file interface, an 'Error' wasn't freed.
> >
> > Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> > ---
> > block/crypto.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/block/crypto.c b/block/crypto.c
> > index 0807557763..9b61fd4aa8 100644
> > --- a/block/crypto.c
> > +++ b/block/crypto.c
> > @@ -736,6 +736,7 @@ fail:
> > if ((r_del < 0) && (r_del != -ENOTSUP)) {
> > error_report_err(local_delete_err);
> > }
> > + error_free(local_delete_err);
> > }
>
> error_report_err() already calls error_free().
Thanks. I didn't knew this.
Will send V3 soon.
Best regards,
Maxim Levitsky
>
> Berto
>
next prev parent reply other threads:[~2020-10-13 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 10:21 [PATCH v2 0/2] qcow2: don't leave partially initialized file on image creation Maxim Levitsky
2020-10-11 10:21 ` [PATCH v2 1/2] crypto: luks: fix tiny memory leak Maxim Levitsky
2020-10-13 12:26 ` Alberto Garcia
2020-10-13 12:31 ` Maxim Levitsky [this message]
2020-10-11 10:21 ` [PATCH v2 2/2] block: qcow2: remove the created file on initialization error Maxim Levitsky
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=96c95d7b4aef3dd0cb2e832c1f0c012f40a8da56.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).