All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Hanna Czenczek <hreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 4/4] iotests/244: Add test cases for keep_data_file
Date: Fri, 6 Mar 2026 17:09:27 +0100	[thread overview]
Message-ID: <aar8NxJVHFDC9HpL@redhat.com> (raw)
In-Reply-To: <20250530084448.192369-5-hreitz@redhat.com>

Am 30.05.2025 um 10:44 hat Hanna Czenczek geschrieben:
> Add various test cases around keep_data_file to the existing data_file
> test suite 244.
> 
> Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
> ---
>  tests/qemu-iotests/244     | 71 ++++++++++++++++++++++++++++++++++++++
>  tests/qemu-iotests/244.out | 53 ++++++++++++++++++++++++++++
>  2 files changed, 124 insertions(+)

> +# No preallocation is OK when also specifying data_file_raw; otherwise, none of
> +# the data file will be mapped, i.e. its contents will stay hidden, so
> +# requesting its contents to be kept (but hidden) doesn't make much sense.
> +#
> +# Metadata preallocation is OK: It will not overwrite the data file's contents,
> +# but ensure the contents are mapped and visible.
> +#
> +# Any data preallocation (like falloc) is not OK, as this would overwrite the
> +# data file's contents despite keep_data_file requesting they should not be
> +# overwritten.
> +#
> +# Note that all of these cases use the data file created above: This verifies
> +# that when passing keep_data_file=on, the data file is always kept as-is (and
> +# e.g. not deleted on error).
> +for prealloc in off metadata falloc; do

Why not add full just for the sake of completeness?

Kevin



  parent reply	other threads:[~2026-03-06 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30  8:44 [PATCH 0/4] qcow2: Add keep_data_file command-line option Hanna Czenczek
2025-05-30  8:44 ` [PATCH 1/4] " Hanna Czenczek
2025-06-12 18:54   ` Eric Blake
2026-03-06 14:29   ` Kevin Wolf
2025-05-30  8:44 ` [PATCH 2/4] qcow2: Simplify size round-up in co_create_opts Hanna Czenczek
2025-06-12 18:56   ` Eric Blake
2025-05-30  8:44 ` [PATCH 3/4] iotests/common.filter: Sort keep_data_file Hanna Czenczek
2025-06-12 19:09   ` Eric Blake
2025-05-30  8:44 ` [PATCH 4/4] iotests/244: Add test cases for keep_data_file Hanna Czenczek
2025-06-12 19:13   ` Eric Blake
2026-03-06 16:09   ` Kevin Wolf [this message]
2025-11-19 15:22 ` [PATCH 0/4] qcow2: Add keep_data_file command-line option Hanna Czenczek
2026-03-06 16:49 ` Kevin Wolf

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=aar8NxJVHFDC9HpL@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hreitz@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 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.