From: Kevin Wolf <kwolf@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, fam@euphon.net,
stefanha@redhat.com, hreitz@redhat.com
Subject: Re: [PATCH v2 0/5] block: refresh filter parents when child was resized
Date: Mon, 27 Oct 2025 17:03:08 +0100 [thread overview]
Message-ID: <aP-XvEvH25SsbSmD@redhat.com> (raw)
In-Reply-To: <20250917115509.401015-1-f.ebner@proxmox.com>
Am 17.09.2025 um 13:54 hat Fiona Ebner geschrieben:
> Changes in v2:
> * Check for BDRV_CHILD_FILTERED rather than bs->drv->is_filter which
> is more generic and for example, also covers the case when the
> child of a 'raw' node is resized.
> * Expand commit message for main patch, i.e. 3/5.
> * Add test for resizing the filtered 'file' node of a 'raw' node.
>
> Resizing a node below a filter would result in the filter still
> reporting the old size. Implement a 'resize' callback for the
> child_of_bds class, that refreshes filter parents recursively.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2025-10-27 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 11:54 [PATCH v2 0/5] block: refresh filter parents when child was resized Fiona Ebner
2025-09-17 11:54 ` [PATCH v2 1/5] include/block/block_int-common: document when resize callback is used Fiona Ebner
2025-09-17 11:54 ` [PATCH v2 2/5] block: make bdrv_co_parent_cb_resize() a proper IO API function Fiona Ebner
2025-09-17 11:54 ` [PATCH v2 3/5] block: implement 'resize' callback for child_of_bds class Fiona Ebner
2025-09-17 11:54 ` [PATCH v2 4/5] iotests: add test for resizing a node below filters Fiona Ebner
2025-09-17 11:54 ` [PATCH v2 5/5] iotests: add test for resizing a 'file' node below a 'raw' node Fiona Ebner
2025-10-21 11:31 ` [PATCH v2 0/5] block: refresh filter parents when child was resized Fiona Ebner
2025-10-27 16:03 ` Kevin Wolf [this message]
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=aP-XvEvH25SsbSmD@redhat.com \
--to=kwolf@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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).