qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, berrange@redhat.com,
	Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v2 03/24] migration: Normalize tls arguments
Date: Fri, 4 Jul 2025 11:37:51 -0400	[thread overview]
Message-ID: <aGf1T8CAQpyf8YoY@x1.local> (raw)
In-Reply-To: <87jz4o3xry.fsf@suse.de>

On Fri, Jul 04, 2025 at 10:12:33AM -0300, Fabiano Rosas wrote:

[...]

> >>> +static void tls_opt_to_str(StrOrNull **tls_opt)
> >>> +{
> >>> +    StrOrNull *opt = *tls_opt;
> >>> +
> >>> +    if (!opt) {
> >>> +        return;
> >>
> >> ... it can also be null.
> >>
> >
> > Hmm, I'll have to double check, but with the StrOrNull property being
> > initialized, NULL should not be possible. This looks like a mistake.
> >
> 
> The code is correct, this is coming from the QAPI, so it could be NULL
> in case the user hasn't provided the option. I'll use your suggested
> wording and the code suggestion as well.

One more trivial question:

> 
> >> Maybe
> >>
> >>    /* Normalize QTYPE_QNULL to QTYPE_QSTRING "" */
> >>
> >>> +    }
> >>> +
> >>> +    switch (opt->type) {
> >>> +    case QTYPE_QSTRING:
> >>> +        return;
> >>> +    case QTYPE_QNULL:
> >>> +        qobject_unref(opt->u.n);
> >>> +        break;
> >>> +    default:
> >>> +        g_assert_not_reached();
> >>> +    }
> >>> +
> >>> +    opt->type = QTYPE_QSTRING;
> >>> +    opt->u.s = g_strdup("");
> >>> +    *tls_opt = opt;

Does tls_opt ever change?   I wonder if this line is not needed, instead
tls_opt_to_str() can take an "StrOrNull *opt" directly.

> >>> +}
> >>
> >> I'd prefer something like
> >>
> >>        if (!opt || opt->type == QTYPE_QSTRING) {
> >>            return;
> >>        }
> >>        qobject_unref(opt->u.n);
> >>        opt->type = QTYPE_QSTRING;
> >>        opt->u.s = g_strdup("");
> >>        *tls_opt = opt;
> >>
> >> But this is clearly a matter of taste.
> 
> This is better indeed. I was moving back-and-forth between
> implementations and the code ended up a bit weird. Thanks!
> 

-- 
Peter Xu



  reply	other threads:[~2025-07-04 15:38 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 19:58 [PATCH v2 00/24] migration: Unify capabilities and parameters Fabiano Rosas
2025-06-30 19:58 ` [PATCH v2 01/24] migration: Fix leak of block_bitmap_mapping Fabiano Rosas
2025-07-01  6:12   ` Markus Armbruster
2025-07-03 21:31     ` Peter Xu
2025-07-04  5:09       ` Markus Armbruster
2025-06-30 19:58 ` [PATCH v2 02/24] migration: Add a qdev property for StrOrNull Fabiano Rosas
2025-07-01  6:38   ` Markus Armbruster
2025-07-03 22:32     ` Peter Xu
2025-07-04 12:58       ` Fabiano Rosas
2025-06-30 19:58 ` [PATCH v2 03/24] migration: Normalize tls arguments Fabiano Rosas
2025-07-01  7:46   ` Markus Armbruster
2025-07-01 14:20     ` Fabiano Rosas
2025-07-04 13:12       ` Fabiano Rosas
2025-07-04 15:37         ` Peter Xu [this message]
2025-08-20 15:45           ` Fabiano Rosas
2025-06-30 19:58 ` [PATCH v2 04/24] migration: Remove MigrateSetParameters Fabiano Rosas
2025-07-01  8:00   ` Markus Armbruster
2025-07-03 19:34     ` Fabiano Rosas
2025-07-04  4:25       ` Markus Armbruster
2025-07-04 15:39   ` Peter Xu
2025-06-30 19:58 ` [PATCH v2 05/24] qapi/migration: Don't document MigrationParameter Fabiano Rosas
2025-07-01  8:04   ` Markus Armbruster
2025-07-04 15:40   ` Peter Xu
2025-06-30 19:58 ` [PATCH v2 06/24] migration: Run a post update routine after setting parameters Fabiano Rosas
2025-06-30 19:58 ` [PATCH v2 07/24] migration: Add a flag to track block-bitmap-mapping input Fabiano Rosas
2025-07-04 15:42   ` Peter Xu
2025-06-30 19:58 ` [PATCH v2 08/24] migration: Remove checks for s->parameters has_* fields Fabiano Rosas
2025-06-30 19:58 ` [PATCH v2 09/24] migration: Do away with usage of QERR_INVALID_PARAMETER_VALUE Fabiano Rosas
2025-07-04 16:04   ` Peter Xu
2025-06-30 19:58 ` [PATCH v2 10/24] migration: Extract code to mark all parameters as present Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 11/24] migration: Use QAPI_CLONE_MEMBERS in query_migrate_parameters Fabiano Rosas
2025-07-04 16:11   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 12/24] migration: Use QAPI_CLONE_MEMBERS in migrate_params_test_apply Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 13/24] migration: Use QAPI_CLONE_MEMBERS in migrate_params_apply Fabiano Rosas
2025-08-13 19:05   ` Peter Xu
2025-08-14 15:04     ` Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 14/24] migration: Use visitors in migrate_params_test_apply Fabiano Rosas
2025-08-13 20:05   ` Peter Xu
2025-08-14 15:10     ` Fabiano Rosas
2025-08-14 19:40       ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 15/24] migration: Cleanup hmp_info_migrate_parameters Fabiano Rosas
2025-08-13 20:40   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 16/24] migration: Add capabilities into MigrationParameters Fabiano Rosas
2025-07-01  8:25   ` Markus Armbruster
2025-07-04 13:15     ` Fabiano Rosas
2025-07-04 14:04       ` Markus Armbruster
2025-07-04 14:48         ` Fabiano Rosas
2025-07-04 15:04           ` Markus Armbruster
2025-07-04 16:33   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 17/24] migration: Remove s->capabilities Fabiano Rosas
2025-08-13 20:48   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 18/24] qapi/migration: Deprecate capabilities commands Fabiano Rosas
2025-07-01  8:30   ` Markus Armbruster
2025-07-01  8:38   ` Jiri Denemark
2025-07-01  9:00     ` Peter Krempa
2025-07-01  9:10     ` Daniel P. Berrangé
2025-08-13 20:50   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 19/24] migration: Store the initial values used for s->parameters Fabiano Rosas
2025-08-13 21:09   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 20/24] migration: Allow migrate commands to provide the migration config Fabiano Rosas
2025-07-01  8:35   ` Markus Armbruster
2025-08-13 21:27   ` Peter Xu
2025-08-14 15:13     ` Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 21/24] tests/qtest/migration: Take reference when passing %p to qtest_qmp Fabiano Rosas
2025-08-13 22:22   ` Peter Xu
2025-08-21 17:20     ` Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 22/24] tests/qtest/migration: Adapt the capabilities helper to take a config Fabiano Rosas
2025-08-14 14:02   ` Peter Xu
2025-06-30 19:59 ` [PATCH v2 23/24] tests/qtest/migration: Adapt convergence routines to config Fabiano Rosas
2025-06-30 19:59 ` [PATCH v2 24/24] tests/qtest/migration: Pass the migration config to file tests Fabiano Rosas
2025-08-14 14:24   ` Peter Xu
2025-08-14 15:30     ` Fabiano Rosas
2025-08-14 19:45       ` Peter Xu

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=aGf1T8CAQpyf8YoY@x1.local \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --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 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).