[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 6/9] file-posix: Forbid trying to change unsuppo
From: |
Max Reitz |
Subject: |
Re: [Qemu-devel] [PATCH 6/9] file-posix: Forbid trying to change unsupported options during reopen |
Date: |
Wed, 29 Aug 2018 13:33:13 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 2018-08-26 16:09, Alberto Garcia wrote:
> The file-posix code is used for the "file", "host_device" and
> "host_cdrom" drivers, and it allows reopening images. However the only
> option that is actually processed is "x-check-cache-dropped", and
> changes in all other options (e.g. "filename") are silently ignored:
>
> (qemu) qemu-io virtio0 "reopen -o file.filename=no-such-file"
>
> While we could allow changing some of the other options, let's keep
> things as they are for now but return an error if the user tries to
> change any of them.
>
> Signed-off-by: Alberto Garcia <address@hidden>
> ---
> block/file-posix.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Looks OK, but the same question from the last patch arises. If
unspecified options mean using the default, shouldn't the user have to
re-specify all mandatory options, so at least @filename in this case?
Max
signature.asc
Description: OpenPGP digital signature
- [Qemu-devel] [PATCH 3/9] block: Remove child references from bs->{options, explicit_options}, (continued)
[Qemu-devel] [PATCH 2/9] file-posix: x-check-cache-dropped should default to false on reopen, Alberto Garcia, 2018/08/26
[Qemu-devel] [PATCH 9/9] block: Allow changing 'force-share' on reopen, Alberto Garcia, 2018/08/26
[Qemu-devel] [PATCH 6/9] file-posix: Forbid trying to change unsupported options during reopen, Alberto Garcia, 2018/08/26
- Re: [Qemu-devel] [PATCH 6/9] file-posix: Forbid trying to change unsupported options during reopen,
Max Reitz <=
[Qemu-devel] [PATCH 7/9] block: Allow changing 'discard' on reopen, Alberto Garcia, 2018/08/26