All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [PATCHv4] qemu-img rebase: use empty string to rebase without backing file
Date: Fri, 19 Oct 2012 11:08:25 -0600	[thread overview]
Message-ID: <50818909.50102@redhat.com> (raw)
In-Reply-To: <508183E0.3000106@redhat.com>

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

On 10/19/2012 10:46 AM, Kevin Wolf wrote:
>> As it happens, we despite what Eric Blake said, we couldn't get an unsafe
>> rebase to no backing file to work with the existing code (with our without
>> our patch). The second option may fix this bug. Reading line 1497, is this
>> because the semantic is not 'an empty string', but 'omit -b entirely'?
>> This behaviour is undocumented in the manpage which specifies -b as a
>> compulsory option. If so, that's a bit unfortunate as we now have different
>> semantics with and without -u. Note if no -b parameter is supplied, there
>> is also a possible null pointer exception at line 1693 (null passed to
>> error_report).
> 
> Right. I think not passing -b at all or passing an empty string should
> have the same meaning, namely removing the backing file reference. I
> won't try to modify this patch to do this, though, we can do it on top.

Agreed - a future patch that makes -b optional rather than mandatory,
where '-b ""' and omitting the argument have the same semantics whether
or not -u is present, would be nice.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


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

      reply	other threads:[~2012-10-19 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 12:46 [Qemu-devel] [PATCHv4] qemu-img rebase: use empty string to rebase without backing file Alex Bligh
2012-10-16 12:54 ` Kevin Wolf
2012-10-17 14:45 ` Kevin Wolf
2012-10-18 21:20   ` Alex Bligh
2012-10-19 16:46     ` Kevin Wolf
2012-10-19 17:08       ` Eric Blake [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=50818909.50102@redhat.com \
    --to=eblake@redhat.com \
    --cc=alex@alex.org.uk \
    --cc=kwolf@redhat.com \
    --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 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.