From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.10?] file-posix: Clear out first sector in hdev_create
Date: Thu, 10 Aug 2017 08:58:36 -0500 [thread overview]
Message-ID: <f587d8ac-476d-e285-6579-3a8188de1790@redhat.com> (raw)
In-Reply-To: <20170810080108.31047-1-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
On 08/10/2017 03:01 AM, Fam Zheng wrote:
> People get surprised when, after "qemu-imc create -f raw /dev/sdX", they
> still see qcow2 with "qemu-img info", if previously the bdev had a qcow2
> header. While this is natural because raw doesn't need to write any
> magic bytes during creation, hdev_create is free to clear out the first
> sector to make sure the stale qcow2 header doesn't cause such a
> confusion.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/file-posix.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/block/file-posix.c b/block/file-posix.c
> index f4de022ae0..1d8ef6f873 100644
> --- a/block/file-posix.c
> +++ b/block/file-posix.c
> @@ -2703,6 +2703,17 @@ static int hdev_create(const char *filename, QemuOpts *opts,
> ret = -ENOSPC;
> }
>
> + if (total_size) {
> + int64_t zero_size = MIN(BDRV_SECTOR_SIZE, total_size);
> + uint8_t *buf;
Since BDRV_SECTOR_SIZE is small enough to stack-allocate, you could skip
the malloc by doing:
uint8_t buf[BDRV_SECTOR_SIZE] = "";
> + if (lseek(fd, 0, SEEK_SET) == -1) {
> + ret = -errno;
> + } else {
> + buf = g_malloc0(zero_size);
> + ret = qemu_write_full(fd, buf, zero_size);
Instead of doing lseek + qemu_write_full, can we just use
qemu_pwritev(fd, &iov, 1, 0) with an iov set up to point to the
appropriate amount of buf?
At any rate, my ideas are micro-optimizations, so I can also live with
how you wrote it.
Reviewed-by: Eric Blake <eblake@redhat.com>
Are you arguing that this is a bug-fix worthy of inclusion in 2.10,
because it helps avoid user confusion? Or are you delaying it to 2.11,
because we've had the existing behavior for longer than one release, so
one release more won't hurt?
--
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 --]
next prev parent reply other threads:[~2017-08-10 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 8:01 [Qemu-devel] [PATCH] file-posix: Clear out first sector in hdev_create Fam Zheng
2017-08-10 13:58 ` Eric Blake [this message]
2017-08-11 7:28 ` [Qemu-devel] [PATCH for-2.10?] " Fam Zheng
2017-08-11 7:44 ` Fam Zheng
2017-08-11 7:44 ` [Qemu-devel] [PATCH] " Xie Changlong
2017-08-11 7:58 ` Fam Zheng
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=f587d8ac-476d-e285-6579-3a8188de1790@redhat.com \
--to=eblake@redhat.com \
--cc=famz@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).