From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, saipava@xilinx.com, stefanha@redhat.com,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [RFC] Block device size rounding
Date: Mon, 12 Oct 2015 10:26:14 -0600 [thread overview]
Message-ID: <561BDF26.4070405@redhat.com> (raw)
In-Reply-To: <561BD814.5090005@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 10/12/2015 09:56 AM, John Snow wrote:
>> What is the correct action here though? If the file is writeable should
>> we just allow the device to extend its size? Is that possible already?
>> Just zero-pad read-only?
>>
>
> Read-only seems like an easy case of append zeroes.
Yes, allowing read-only with append-zero behavior seems sane.
>
> Read-write ... well, we can't write-protect just half of a 512k block.
> Probably just forcibly increasing the size on RW or refusing to use the
> file altogether are probably the sane deterministic things we want.
I'd lean towards outright rejection if the file size isn't up to snuff
for use as read-write. Forcibly increasing the size (done
unconditionally) still feels like magic, and may not be possible if the
size is due to something backed by a block device rather than a file.
--
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: 604 bytes --]
next prev parent reply other threads:[~2015-10-12 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 3:01 [Qemu-devel] [RFC] Block device size rounding Peter Crosthwaite
2015-10-12 15:56 ` John Snow
2015-10-12 16:26 ` Eric Blake [this message]
2015-10-12 18:09 ` Peter Crosthwaite
2015-10-12 18:26 ` John Snow
2015-10-13 7:16 ` Markus Armbruster
2015-10-13 9:14 ` Kevin Wolf
2015-10-13 15:30 ` Peter Crosthwaite
2015-10-13 15:51 ` John Snow
2015-10-14 8:36 ` Kevin Wolf
2015-10-16 17:04 ` John Snow
2015-10-16 18:10 ` Peter Crosthwaite
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=561BDF26.4070405@redhat.com \
--to=eblake@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saipava@xilinx.com \
--cc=stefanha@redhat.com \
/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.