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 v2 1/1] block/crypto: better error message when creating too large files
Date: Thu, 30 Apr 2020 16:03:50 +0300 [thread overview]
Message-ID: <cbb54ad47e8da413d7529783332dd7c854f3b199.camel@redhat.com> (raw)
In-Reply-To: <20200420092951.24578-2-mlevitsk@redhat.com>
On Mon, 2020-04-20 at 12:29 +0300, Maxim Levitsky wrote:
> Currently if you attampt to create too large file with luks you
> get the following error message:
>
> Formatting 'test.luks', fmt=luks size=17592186044416 key-secret=sec0
> qemu-img: test.luks: Could not resize file: File too large
>
> While for raw format the error message is
> qemu-img: test.img: The image size is too large for file format 'raw'
>
>
> The reason for this is that qemu-img checks for errono of the failure,
> and presents the later error when it is -EFBIG
>
> However crypto generic code 'swallows' the errno and replaces it
> with -EIO.
>
> As an attempt to make it better, we can make luks driver,
> detect -EFBIG and in this case present a better error message,
> which is what this patch does
>
> The new error message is:
>
> qemu-img: error creating test.luks: The requested file size is too large
>
> Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1534898
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> block/crypto.c | 25 +++++++++++++++++++++----
> 1 file changed, 21 insertions(+), 4 deletions(-)
>
> diff --git a/block/crypto.c b/block/crypto.c
> index d577f89659..f9f5dc11a7 100644
> --- a/block/crypto.c
> +++ b/block/crypto.c
> @@ -104,18 +104,35 @@ static ssize_t block_crypto_init_func(QCryptoBlock *block,
> Error **errp)
> {
> struct BlockCryptoCreateData *data = opaque;
> + Error *local_err = NULL;
> + int ret;
>
> if (data->size > INT64_MAX || headerlen > INT64_MAX - data->size) {
> - error_setg(errp, "The requested file size is too large");
> - return -EFBIG;
> + ret = -EFBIG;
> + goto error;
> }
>
> /* User provided size should reflect amount of space made
> * available to the guest, so we must take account of that
> * which will be used by the crypto header
> */
> - return blk_truncate(data->blk, data->size + headerlen, false,
> - data->prealloc, errp);
> + ret = blk_truncate(data->blk, data->size + headerlen, false,
> + data->prealloc, &local_err);
> +
> + if (ret >= 0) {
> + return ret;
> + }
> +
> +error:
> + if (ret == -EFBIG) {
> + /* Replace the error message with a better one */
> + error_free(local_err);
> + error_setg(errp, "The requested file size is too large");
> + } else {
> + error_propagate(errp, local_err);
> + }
> +
> + return ret;
> }
>
>
Could someone pick that patch now that the freeze is over?
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2020-04-30 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 9:29 [PATCH v2 0/1] LUKS: Fix error message when underlying fs don't support large enough files Maxim Levitsky
2020-04-20 9:29 ` [PATCH v2 1/1] block/crypto: better error message when creating too large files Maxim Levitsky
2020-04-30 13:03 ` Maxim Levitsky [this message]
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=cbb54ad47e8da413d7529783332dd7c854f3b199.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).