qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] qemu-img: Check for backing image if specified during create
Date: Tue, 18 Jul 2017 10:44:39 -0500	[thread overview]
Message-ID: <215d40eb-09d5-ad9f-1f91-f3ddb683a7dc@redhat.com> (raw)
In-Reply-To: <e5627ad4-89bc-a25e-3d14-12abc82f4e64@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]

On 07/18/2017 10:33 AM, John Snow wrote:
> 
> 
> On 07/18/2017 08:51 AM, Eric Blake wrote:
>> On 07/17/2017 07:34 PM, John Snow wrote:
>>> Or, rather, force the open of a backing image if one was specified
>>> for creation. Using a similar -unsafe option as rebase, allow qemu-img
>>> to ignore the backing file validation if possible.

>>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>
>> Really? It seems like you've changed since v4.
>>
> 
> Duh. I missed this because the patchset grew to two patches, same with
> revising the message. I'm sorry about that.

Kevin's got it on his block branch, with that fixed already. No problem.

>>>      size = qemu_opt_get_size(opts, BLOCK_OPT_SIZE, 0);
>>
>> On v4, we talked about making this use qemu_opt_get_size(, -1) to make
>> it less confusing about how qemu_opt_get_size() refers back to a
>> caller-provided default embedded in QemuOpt (rather than the parameter).>
> 
> I actually got scared away from this because of the get_size signature,
> is it safe to pass -1 here?

I'm posting a separate patch for that now (yours is fine left alone,
because it is pre-existing).

> 
>>> +        if (!bs && size != -1) {
>>> +            /* Couldn't open BS, but we have a size, so it's nonfatal */
>>> +            error_reportf_err(local_err,
>>> +                              "Warning: could not verify backing image. "
>>> +                              "This may become an error in future versions.\n");
>>
>> Patchew rightly complained here about the trailing newline. Also, we
>> have the new warning* functions merged in, this should probably be using
>> those (see commit 3dc6f869, for example)
>>
> 
> I tried omitting it, but the printing looked wrong, and the test would
> mash input against the tail of the sentence.

Kevin adjusted it slightly on the block branch. If patchew still
complains, we may need to fix checkpatch.pl (the semantics of
error_reportf_err() are slightly different than error_setg(), after all).

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-07-18 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  0:34 [Qemu-devel] [PATCH v5 0/2] qemu-img: Check for backing image if specified during create John Snow
2017-07-18  0:34 ` [Qemu-devel] [PATCH v5 1/2] blockdev: move BDRV_O_NO_BACKING option forward John Snow
2017-07-18 12:27   ` Eric Blake
2017-07-18  0:34 ` [Qemu-devel] [PATCH v5 2/2] qemu-img: Check for backing image if specified during create John Snow
2017-07-18 12:51   ` Eric Blake
2017-07-18 15:33     ` John Snow
2017-07-18 15:44       ` Eric Blake [this message]
2017-07-18  0:38 ` [Qemu-devel] [PATCH v5 0/2] " John Snow
2017-07-18 12:25 ` no-reply
2017-07-18 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=215d40eb-09d5-ad9f-1f91-f3ddb683a7dc@redhat.com \
    --to=eblake@redhat.com \
    --cc=jsnow@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).