From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
hreitz@redhat.com, kwolf@redhat.com, eblake@redhat.com,
jsnow@redhat.com, devel@lists.libvirt.org, pkrempa@redhat.com,
michael.roth@amd.com, pbonzini@redhat.com
Subject: Re: [PATCH] [for-10.1] qapi/block-core: derpecate some block-job- APIs
Date: Sat, 05 Apr 2025 09:13:04 +0200 [thread overview]
Message-ID: <875xjjhyin.fsf@pond.sub.org> (raw)
In-Reply-To: <184192da-6f38-4c7b-926e-ad5a42482a64@yandex-team.ru> (Vladimir Sementsov-Ogievskiy's message of "Fri, 4 Apr 2025 18:03:13 +0300")
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:
> On 04.04.25 17:13, Markus Armbruster wrote:
[...]
>> So, auto-finalize=true is silently ignored when another job in the same
>> transaction has auto-finalize=false?
>
> Yes, at least, it looks like so:
>
> static void job_completed_txn_success_locked(Job *job)
> {
>
> [...]
>
> /* If no jobs need manual finalization, automatically do so */
> if (job_txn_apply_locked(job, job_needs_finalize_locked) == 0) {
> job_do_finalize_locked(job);
> }
> }
Silently ignoring what the user specified is not okay whether the user's
instructions make sense or not.
Fixing this UI bug would break usage that relies on it. Should we care?
[...]
prev parent reply other threads:[~2025-04-05 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 15:57 [PATCH] [for-10.1] qapi/block-core: derpecate some block-job- APIs Vladimir Sementsov-Ogievskiy
2025-04-01 16:32 ` Peter Krempa
2025-04-04 6:20 ` Markus Armbruster
2025-04-04 11:33 ` Vladimir Sementsov-Ogievskiy
2025-04-04 14:13 ` Markus Armbruster
2025-04-04 15:03 ` Vladimir Sementsov-Ogievskiy
2025-04-05 7:13 ` Markus Armbruster [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=875xjjhyin.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@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.