From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] qcow2: cleanup created file when qcow2_co_create
Date: Tue, 01 Sep 2020 14:20:13 +0300 [thread overview]
Message-ID: <283e2c4566bfa47e3a996efc7a6220921a00e0b0.camel@redhat.com> (raw)
In-Reply-To: <20200716113359.15656-1-mlevitsk@redhat.com>
On Thu, 2020-07-16 at 14:33 +0300, Maxim Levitsky wrote:
> This is basically the same thing as commit
> 'crypto.c: cleanup created file when block_crypto_co_create_opts_luks fails'
> does but for qcow2 files to ensure that we don't leave qcow2 files
> when creation fails.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Very kind ping on this patch.
Best regards,
Maxim levitsky
> ---
> block/qcow2.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/block/qcow2.c b/block/qcow2.c
> index fadf3422f8..8b848924b5 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -3794,6 +3794,17 @@ static int coroutine_fn qcow2_co_create_opts(BlockDriver *drv,
> /* Create the qcow2 image (format layer) */
> ret = qcow2_co_create(create_options, errp);
> if (ret < 0) {
> +
> + Error *local_delete_err = NULL;
> + int r_del = bdrv_co_delete_file(bs, &local_delete_err);
> + /*
> + * ENOTSUP will happen if the block driver doesn't support
> + * the 'bdrv_co_delete_file' interface. This is a predictable
> + * scenario and shouldn't be reported back to the user.
> + */
> + if ((r_del < 0) && (r_del != -ENOTSUP)) {
> + error_report_err(local_delete_err);
> + }
> goto finish;
> }
>
next prev parent reply other threads:[~2020-09-01 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 11:33 [PATCH] qcow2: cleanup created file when qcow2_co_create Maxim Levitsky
2020-07-29 5:11 ` Maxim Levitsky
2020-09-01 11:20 ` Maxim Levitsky [this message]
2020-09-01 13:30 ` Alberto Garcia
2020-10-11 8:38 ` 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=283e2c4566bfa47e3a996efc7a6220921a00e0b0.camel@redhat.com \
--to=mlevitsk@redhat.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).