From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] qemu-img: Fix convert -n -B for backing-less targets
Date: Tue, 21 Jan 2020 17:43:55 -0500 [thread overview]
Message-ID: <b584be34-1928-0e1f-3d19-ab4e3803d7a1@redhat.com> (raw)
In-Reply-To: <20200121155915.98232-1-mreitz@redhat.com>
On 1/21/20 10:59 AM, Max Reitz wrote:
> Hi,
>
> When reviewing David’s series to add --target-is-zero convert, I looked
> for a case to show that the current implementation will crash if
> -n --target-is-zero is used together with -B. It then turned out that
> -B will always crash when combined with -n and the target image does not
> have a backing file set in its image header.
>
> This series fixes that.
>
>
> Max Reitz (2):
> qemu-img: Fix convert -n -B for backing-less targets
> iotests: Test convert -n -B to backing-less target
>
> qemu-img.c | 2 +-
> tests/qemu-iotests/122 | 14 ++++++++++++++
> tests/qemu-iotests/122.out | 5 +++++
> 3 files changed, 20 insertions(+), 1 deletion(-)
>
Hello.
Makes sense to me.
Reviewed-by: John Snow <jsnow@redhat.com>
(My brain had an awfully tumultuous 35 seconds comprehending that
"is_new" was not a synonym for "-n was provided", but actually means the
opposite.)
next prev parent reply other threads:[~2020-01-21 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 15:59 [PATCH 0/2] qemu-img: Fix convert -n -B for backing-less targets Max Reitz
2020-01-21 15:59 ` [PATCH 1/2] " Max Reitz
2020-01-21 15:59 ` [PATCH 2/2] iotests: Test convert -n -B to backing-less target Max Reitz
2020-01-21 22:43 ` John Snow [this message]
2020-02-19 10:39 ` [PATCH 0/2] qemu-img: Fix convert -n -B for backing-less targets Max Reitz
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=b584be34-1928-0e1f-3d19-ab4e3803d7a1@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).