From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
pbonzini@redhat.com, armbru@redhat.com, eblake@redhat.com,
hreitz@redhat.com
Subject: Re: [PATCH v9 4/7] qapi: add blockdev-replace command
Date: Mon, 17 Nov 2025 11:49:30 +0100 [thread overview]
Message-ID: <aRr9uuaz4FmEextJ@redhat.com> (raw)
In-Reply-To: <ebbc334f-43d2-4a06-a3a0-5fa3c1266f52@yandex-team.ru>
Hi Vladimir,
I remembered this series and wanted to check what the current status is,
because I seemed to remember that the next step was that you would send
a new version. But reading it again, you're probably waiting for more
input? Let's try to get this finished.
Am 02.04.2025 um 15:05 hat Vladimir Sementsov-Ogievskiy geschrieben:
> On 18.10.24 16:59, Kevin Wolf wrote:
> > If we want to get rid of the union, I think the best course of action
> > would unifying the namespaces (so that nodes, exports and devices can't
> > share the same ID) and then we could just accept a universal 'id' along
> > with 'child'.
>
> Maybe we can go this way even without explicit restriction (which
> should some how go through deprecation period, etc), but simply look
> for the id among nodes, devices and exports and if found more than one
> parent - fail.
>
> And we document, that id should not be ambiguous, should not match more
> than one parent object. So, those who want to use new command will care
> to make unique ids.
I don't think such a state is very pretty, but it would be okay for me
as an intermediate state while we go through a deprecation period to
restrict IDs accordingly.
So we could start with blockdev-replace returning an error on ambiguous
IDs and at the same time deprecate them, and only later we would make
creating nodes/devices/exports with the same ID an error.
Kevin
next prev parent reply other threads:[~2025-11-17 10:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 11:53 [PATCH v9 0/7] blockdev-replace Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 1/7] block-backend: blk_root(): drop const specifier on return type Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 2/7] block/export: add blk_by_export_id() Vladimir Sementsov-Ogievskiy
2024-07-18 11:48 ` Markus Armbruster
2024-07-19 10:59 ` Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 3/7] block: make bdrv_find_child() function public Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 4/7] qapi: add blockdev-replace command Vladimir Sementsov-Ogievskiy
2024-07-18 12:00 ` Markus Armbruster
2024-07-19 16:00 ` Vladimir Sementsov-Ogievskiy
2024-10-02 14:41 ` Vladimir Sementsov-Ogievskiy
2024-10-04 17:01 ` Vladimir Sementsov-Ogievskiy
2024-10-18 13:59 ` Kevin Wolf
2025-04-02 13:05 ` Vladimir Sementsov-Ogievskiy
2025-11-17 10:49 ` Kevin Wolf [this message]
2025-11-18 7:37 ` Vladimir Sementsov-Ogievskiy
2025-11-18 9:47 ` Kevin Wolf
2025-11-18 12:19 ` Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 5/7] block: bdrv_get_xdbg_block_graph(): report export ids Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 6/7] iotests.py: introduce VM.assert_edges_list() method Vladimir Sementsov-Ogievskiy
2024-06-26 11:53 ` [PATCH v9 7/7] iotests: add filter-insertion Vladimir Sementsov-Ogievskiy
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=aRr9uuaz4FmEextJ@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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.