From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH] file-posix: Clear out first sector in hdev_create
Date: Thu, 10 Aug 2017 16:01:08 +0800 [thread overview]
Message-ID: <20170810080108.31047-1-famz@redhat.com> (raw)
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;
+ if (lseek(fd, 0, SEEK_SET) == -1) {
+ ret = -errno;
+ } else {
+ buf = g_malloc0(zero_size);
+ ret = qemu_write_full(fd, buf, zero_size);
+ g_free(buf);
+ }
+ }
qemu_close(fd);
return ret;
}
--
2.13.3
next reply other threads:[~2017-08-10 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 8:01 Fam Zheng [this message]
2017-08-10 13:58 ` [Qemu-devel] [PATCH for-2.10?] file-posix: Clear out first sector in hdev_create Eric Blake
2017-08-11 7:28 ` 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=20170810080108.31047-1-famz@redhat.com \
--to=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).