From: "Denis V. Lunev" <den@virtuozzo.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com,
vsementsov@yandex-team.ru, kwolf@redhat.com, hreitz@redhat.com
Subject: Re: [PATCH v4 12/21] parallels: Let image extensions work in RW mode
Date: Wed, 28 Feb 2024 13:11:36 +0100 [thread overview]
Message-ID: <c244e29f-6b87-4010-ab6e-ac1498247eed@virtuozzo.com> (raw)
In-Reply-To: <42466483-7583-497d-89f5-cbd447f5647e@virtuozzo.com>
On 2/28/24 11:25, Alexander Ivanov wrote:
>
>
> On 1/18/24 14:31, Denis V. Lunev wrote:
>> On 1/16/24 15:45, Denis V. Lunev wrote:
>>> On 12/28/23 11:12, Alexander Ivanov wrote:
>>>> Now we support extensions saving and can let to work with them in
>>>> read-write mode.
>>>>
>>>> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
>>>> ---
>>>> block/parallels-ext.c | 4 ----
>>>> block/parallels.c | 17 ++++-------------
>>>> 2 files changed, 4 insertions(+), 17 deletions(-)
>>>>
>>>> diff --git a/block/parallels-ext.c b/block/parallels-ext.c
>>>> index c83d1ea393..195b01b109 100644
>>>> --- a/block/parallels-ext.c
>>>> +++ b/block/parallels-ext.c
>>>> @@ -175,10 +175,6 @@ parallels_load_bitmap(BlockDriverState *bs,
>>>> uint8_t *data, size_t data_size,
>>>> return NULL;
>>>> }
>>>> - /* We support format extension only for RO parallels images. */
>>>> - assert(!(bs->open_flags & BDRV_O_RDWR));
>>>> - bdrv_dirty_bitmap_set_readonly(bitmap, true);
>>>> -
>>>> return bitmap;
>>>> }
>>>> diff --git a/block/parallels.c b/block/parallels.c
>>>> index a49922c6a7..d5d87984cf 100644
>>>> --- a/block/parallels.c
>>>> +++ b/block/parallels.c
>>>> @@ -1374,19 +1374,10 @@ static int parallels_open(BlockDriverState
>>>> *bs, QDict *options, int flags,
>>>> }
>>>> if (ph.ext_off) {
>>>> - if (flags & BDRV_O_RDWR) {
>>>> - /*
>>>> - * It's unsafe to open image RW if there is an
>>>> extension (as we
>>>> - * don't support it). But parallels driver in QEMU
>>>> historically
>>>> - * ignores the extension, so print warning and don't
>>>> care.
>>>> - */
>>>> - warn_report("Format Extension ignored in RW mode");
>>>> - } else {
>>>> - ret = parallels_read_format_extension(
>>>> - bs, le64_to_cpu(ph.ext_off) <<
>>>> BDRV_SECTOR_BITS, errp);
>>>> - if (ret < 0) {
>>>> - goto fail;
>>>> - }
>>>> + ret = parallels_read_format_extension(
>>>> + bs, le64_to_cpu(ph.ext_off) << BDRV_SECTOR_BITS,
>>>> errp);
>>>> + if (ret < 0) {
>>>> + goto fail;
>>>> }
>>>> }
>>> Reviewed-by: Denis V. Lunev <den@openvz.org>
>> This patch also deserves a note, what will happen with
>> format extensions clusters. According to the current
>> policy, we have only transient extensions, i.e.
>> CBT. Cluster allocation mechanism will reuse these
>> clusters as they are not marked as used.
>> Thus we should either set format extension offset
>> in the header to 0 or perform any other correct
>> measures to properly handle this.
> Yes, all the clusters used by extensions are marked as unused
> on loading. In further work they can be reallocated for other
> purposes.
> Agree that we need to set ext_off to zero.
>>
>> It should also be noted, that on any QEMU crash
>> appropriate format extensions are to be properly
>> treated. We could not make them RW until this would
>> not be addressed as we could easily mess up with
>> trashed metadata.
> If QEMU crashes after extensions loading there will be
> zero in the ext_off field and an inappropriate dirty bitmap
> will be ignored.
>
That should be considered as a minimal kludge.
Normally we should mark format extension cluster
as used and nullify references from the bitmaps
there.
Anyway, even if the ext_off is not zero and
bitmaps are present, bitmaps loading over
unclean image should not be performed. They should
be considered outdated.
Den
next prev parent reply other threads:[~2024-02-28 12:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 10:12 [PATCH v4 00/21] parallels: Add full dirty bitmap support Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 01/21] parallels: Set s->used_bmap to NULL in parallels_free_used_bitmap() Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 02/21] parallels: Move inactivation code to a separate function Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 03/21] parallels: Make mark_used() a global function Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 04/21] parallels: Limit search in parallels_mark_used to the last marked claster Alexander Ivanov
2024-01-16 13:52 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 05/21] parallels: Add parallels_mark_unused() helper Alexander Ivanov
2024-01-16 13:54 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 06/21] parallels: Move host clusters allocation to a separate function Alexander Ivanov
2024-01-16 14:19 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 07/21] parallels: Set data_end value in parallels_check_leak() Alexander Ivanov
2024-01-16 14:21 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 08/21] parallels: Recreate used bitmap " Alexander Ivanov
2024-01-16 14:24 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 09/21] parallels: Add a note about used bitmap in parallels_check_duplicate() Alexander Ivanov
2024-01-16 14:30 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 10/21] parallels: Create used bitmap even if checks needed Alexander Ivanov
2024-01-16 14:37 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 11/21] parallels: Add dirty bitmaps saving Alexander Ivanov
2024-01-18 13:27 ` Denis V. Lunev
2024-02-07 12:42 ` Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 12/21] parallels: Let image extensions work in RW mode Alexander Ivanov
2024-01-16 14:45 ` Denis V. Lunev
2024-01-18 13:31 ` Denis V. Lunev
2024-02-28 10:25 ` Alexander Ivanov
2024-02-28 12:11 ` Denis V. Lunev [this message]
2024-01-18 13:35 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 13/21] parallels: Handle L1 entries equal to one Alexander Ivanov
2024-01-18 13:37 ` Denis V. Lunev
2024-02-29 11:57 ` Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 14/21] parallels: Make a loaded dirty bitmap persistent Alexander Ivanov
2024-01-18 13:59 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 15/21] parallels: Reverse a conditional in parallels_check_leak() to reduce indents Alexander Ivanov
2024-01-18 14:49 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 16/21] parallels: Truncate images on the last used cluster Alexander Ivanov
2024-01-18 14:52 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 17/21] parallels: Check unused clusters in parallels_check_leak() Alexander Ivanov
2024-01-18 14:55 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 18/21] parallels: Remove unnecessary data_end field Alexander Ivanov
2024-01-18 15:00 ` Denis V. Lunev
2023-12-28 10:12 ` [PATCH v4 19/21] tests: Add parallels images support to test 165 Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 20/21] tests: Turned on 256, 299, 304 and block-status-cache for parallels format Alexander Ivanov
2023-12-28 10:12 ` [PATCH v4 21/21] tests: Add parallels format support to image-fleecing Alexander Ivanov
2023-12-29 15:59 ` Vladimir Sementsov-Ogievskiy
2024-01-18 15:01 ` [PATCH v4 00/21] parallels: Add full dirty bitmap support Denis V. Lunev
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=c244e29f-6b87-4010-ab6e-ac1498247eed@virtuozzo.com \
--to=den@virtuozzo.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).