From: Eric Blake <eblake@redhat.com>
To: 858585 jemmy <jemmy858585@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Lidong Chen <lidongchen@tencent.com>,
qemu block <qemu-block@nongnu.org>,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes
Date: Tue, 25 Apr 2017 14:20:08 -0500 [thread overview]
Message-ID: <f4bac29a-23e1-a2fb-e4ae-fb6298c04984@redhat.com> (raw)
In-Reply-To: <CAOGPPbced2TTLkU8VmaQVGmAatpckd+T=2+uue-=drOkVd4rLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
On 04/24/2017 08:50 PM, 858585 jemmy wrote:
> On Mon, Apr 24, 2017 at 10:43 PM, Eric Blake <eblake@redhat.com> wrote:
>> On 04/23/2017 09:33 AM, jemmy858585@gmail.com wrote:
>>> From: Lidong Chen <lidongchen@tencent.com>
>>>
>>> is_allocated_sectors_min don't guarantee to contain the
>>> consecutive number of zero bytes. this patch fixes this bug.
>>
>> This message was sent without an 'In-Reply-To' header pointing to a 0/2
>> cover letter. When sending a series, please always thread things to a
>> cover letter; you may find 'git config format.coverletter auto' to be
>> helpful.
>
> Thanks for your kind advises.
>
>>
>> I seem to recall past attempts to try and patch this function, which
>> were then turned down, although I haven't scrubbed the archives for a
>> quick URL to point to. I'm worried that there are more subtleties here
>> than what you realize.
>
> Hi Eric:
> Do you mean this URL?
> https://lists.gnu.org/archive/html/qemu-block/2017-01/msg00306.html
Yes, that's probably the one.
>
> But I think the code is not consistent with qemu-img --help.
> qemu-img --help
> '-S' indicates the consecutive number of bytes (defaults to 4k) that must
> contain only zeros for qemu-img to create a sparse image during
> conversion. If the number of bytes is 0, the source will not be
> scanned for
> unallocated or zero sectors, and the destination image will always be
> fully allocated.
If you still think this patch is needed, the best way to convince me of
it is accompany your patch by a qemu-iotests enhancement that covers the
change in behavior (running the test pre-patch would show that we are
broken without the patch, and having the test ensures we can't later
regress). That's a lot more work than the vague two lines of the commit
message body.
--
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: 604 bytes --]
next prev parent reply other threads:[~2017-04-25 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 14:33 [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes jemmy858585
2017-04-23 14:33 ` [Qemu-devel] [PATCH 2/2] qemu-img: fix some spelling errors jemmy858585
2017-04-24 14:40 ` Eric Blake
2017-04-24 15:37 ` Philippe Mathieu-Daudé
2017-04-24 15:47 ` Eric Blake
2017-04-24 15:53 ` Eric Blake
2017-04-25 2:10 ` 858585 jemmy
2017-04-25 19:11 ` Max Reitz
2017-04-26 8:05 ` 858585 jemmy
2017-04-24 14:43 ` [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes Eric Blake
2017-04-25 1:50 ` 858585 jemmy
2017-04-25 19:20 ` Eric Blake [this message]
2017-04-25 20:01 ` 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=f4bac29a-23e1-a2fb-e4ae-fb6298c04984@redhat.com \
--to=eblake@redhat.com \
--cc=jemmy858585@gmail.com \
--cc=kwolf@redhat.com \
--cc=lidongchen@tencent.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).