From: Het Gala <het.gala@nutanix.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, prerna.saxena@nutanix.com,
quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com,
armbru@redhat.com, eblake@redhat.com, manish.mishra@nutanix.com,
aravind.retnakaran@nutanix.com
Subject: Re: [PATCH v4 5/8] migration: converts exec backend to accept MigrateAddress struct.
Date: Mon, 15 May 2023 20:34:45 +0530 [thread overview]
Message-ID: <2a3dce41-0e4d-849e-c8ab-3c6ea7965642@nutanix.com> (raw)
In-Reply-To: <ZGIJehrjvkchRbeX@redhat.com>
On 15/05/23 3:59 pm, Daniel P. Berrangé wrote:
> On Fri, May 12, 2023 at 02:32:37PM +0000, Het Gala wrote:
>> Exec transport backend for 'migrate'/'migrate-incoming' QAPIs accept
>> new wire protocol of MigrateAddress struct.
>>
>> It is achived by parsing 'uri' string and storing migration parameters
>> required for exec connection into strList struct.
>>
>> Suggested-by: Aravind Retnakaran <aravind.retnakaran@nutanix.com>
>> Signed-off-by: Het Gala <het.gala@nutanix.com>
>> ---
>> migration/exec.c | 58 ++++++++++++++++++++++++++++++++-----------
>> migration/exec.h | 4 +--
>> migration/migration.c | 10 +++-----
>> 3 files changed, 50 insertions(+), 22 deletions(-)
>>
>> diff --git a/migration/exec.c b/migration/exec.c
>> index c4a3293246..210f4e9400 100644
>> --- a/migration/exec.c
>> +++ b/migration/exec.c
>> @@ -39,22 +39,51 @@ const char *exec_get_cmd_path(void)
>> }
>> #endif
>>
>> -void exec_start_outgoing_migration(MigrationState *s, const char *command,
>> +/* provides the length of strList */
>> +static int
>> +str_list_length(strList *list)
>> +{
>> + int len = 0;
>> + strList *elem;
>> +
>> + for (elem = list; elem != NULL; elem = elem->next) {
>> + len++;
>> + }
>> +
>> + return len;
>> +}
>> +
Juan for your comment : "I can't believe tat we have a list type and we
don't have a length() function for that type."
I had seen come patches regarding adding utility for finding length of a
strList in util.h file as a MACRO, but I think the patches have still
not gone in.
>> +static void
>> +init_exec_array(strList *command, const char **argv, Error **errp)
>> +{
>> + int i = 0;
>> + strList *lst;
>> +
>> + for (lst = command; lst; lst = lst->next) {
>> + argv[i++] = lst->value;
>> + }
>> +
>> + argv[i] = NULL;
>> + return;
>> +}
>> +
>> +void exec_start_outgoing_migration(MigrationState *s, strList *command,
>> Error **errp)
>> {
>> QIOChannel *ioc;
>>
>> -#ifdef WIN32
>> - const char *argv[] = { exec_get_cmd_path(), "/c", command, NULL };
>> -#else
>> - const char *argv[] = { "/bin/sh", "-c", command, NULL };
>> -#endif
>> + int length = str_list_length(command);
>> + const char **argv = g_malloc0(length * sizeof(const char *));
> g_malloc0 is almost never desirable to use, instead:
>
> g_new0(const char *, length);
Ack. Will change that.
>>
>> - trace_migration_exec_outgoing(command);
>> + init_exec_array(command, argv, errp);
>> + char *new_command = g_strjoinv(" ", (char **)argv);
> Never freed - use
>
> g_autofree char *new_command...
Ack.
>> + trace_migration_exec_outgoing(new_command);
>>
>> ioc = QIO_CHANNEL(qio_channel_command_new_spawn(argv,
>> O_RDWR,
>> errp));
>> if (!ioc) {
>> + g_free(argv);
>> return;
>> }
> argv needs freeing in success too. Simpler to declare it
> with
>
> g_auto(GStrv) argv = .....
Yes, Ack.
>>
>> @@ -72,21 +101,22 @@ static gboolean exec_accept_incoming_migration(QIOChannel *ioc,
>> return G_SOURCE_REMOVE;
>> }
>>
>> -void exec_start_incoming_migration(const char *command, Error **errp)
>> +void exec_start_incoming_migration(strList *command, Error **errp)
>> {
>> QIOChannel *ioc;
>>
>> -#ifdef WIN32
>> - const char *argv[] = { exec_get_cmd_path(), "/c", command, NULL };
>> -#else
>> - const char *argv[] = { "/bin/sh", "-c", command, NULL };
>> -#endif
>> + int length = str_list_length(command);
>> + const char **argv = g_malloc0(length * sizeof(const char *));
>> +
>> + init_exec_array(command, argv, errp);
>> + char *new_command = g_strjoinv(" ", (char **)argv);
>>
>> - trace_migration_exec_incoming(command);
>> + trace_migration_exec_incoming(new_command);
>> ioc = QIO_CHANNEL(qio_channel_command_new_spawn(argv,
>> O_RDWR,
>> errp));
>> if (!ioc) {
>> + g_free(argv);
>> return;
>> }
> All the same comments as the outgoing case.
Ack. Thanks Daniel for the inputs.
> With regards,
> Daniel
Regards,
Het Gala
next prev parent reply other threads:[~2023-05-15 15:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 14:32 [PATCH v4 0/8] migration: Modified 'migrate' and 'migrate-incoming' QAPI commands for migration Het Gala
2023-05-12 14:32 ` [PATCH v4 1/8] migration: introduced 'MigrateAddress' in QAPI for migration wire protocol Het Gala
2023-05-15 8:37 ` Juan Quintela
2023-05-15 10:06 ` Daniel P. Berrangé
2023-05-12 14:32 ` [PATCH v4 2/8] migration: Converts uri parameter into 'MigrateAddress' struct Het Gala
2023-05-15 8:43 ` Juan Quintela
2023-05-15 10:12 ` Daniel P. Berrangé
2023-05-15 11:45 ` Het Gala
2023-05-15 11:55 ` Juan Quintela
2023-05-15 12:17 ` Daniel P. Berrangé
2023-05-15 12:25 ` Juan Quintela
2023-05-12 14:32 ` [PATCH v4 3/8] migration: converts socket backend to accept MigrateAddress struct Het Gala
2023-05-15 8:55 ` Juan Quintela
2023-05-15 10:17 ` Daniel P. Berrangé
2023-05-15 14:22 ` Het Gala
2023-05-15 14:46 ` Juan Quintela
2023-05-15 15:16 ` Het Gala
2023-05-15 16:28 ` Het Gala
2023-05-15 16:42 ` Daniel P. Berrangé
2023-05-12 14:32 ` [PATCH v4 4/8] migration: converts rdma " Het Gala
2023-05-15 9:51 ` Juan Quintela
2023-05-15 10:24 ` Daniel P. Berrangé
2023-05-15 14:38 ` Het Gala
2023-05-15 14:58 ` Daniel P. Berrangé
2023-05-15 15:17 ` Het Gala
2023-05-12 14:32 ` [PATCH v4 5/8] migration: converts exec " Het Gala
2023-05-15 9:58 ` Juan Quintela
2023-05-15 10:29 ` Daniel P. Berrangé
2023-05-15 15:04 ` Het Gala [this message]
2023-05-12 14:32 ` [PATCH v4 6/8] migration: modified 'migrate' QAPI to accept 'channels' argument for migration Het Gala
2023-05-15 10:36 ` Daniel P. Berrangé
2023-05-16 5:48 ` Het Gala
2023-05-16 8:57 ` Daniel P. Berrangé
2023-05-16 10:14 ` Het Gala
2023-05-12 14:32 ` [PATCH v4 7/8] migration: modified 'migrate-incoming' " Het Gala
2023-05-15 10:01 ` Juan Quintela
2023-05-15 10:38 ` Daniel P. Berrangé
2023-05-12 14:32 ` [PATCH v4 8/8] migration: Introduced MigrateChannelList struct to migration code flow Het Gala
2023-05-15 10:04 ` Juan Quintela
2023-05-15 10:42 ` Daniel P. Berrangé
2023-05-16 17:18 ` Het Gala
2023-05-17 8:34 ` Juan Quintela
2023-05-16 10:32 ` [PATCH v4 0/8] migration: Modified 'migrate' and 'migrate-incoming' QAPI commands for migration Markus Armbruster
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=2a3dce41-0e4d-849e-c8ab-3c6ea7965642@nutanix.com \
--to=het.gala@nutanix.com \
--cc=aravind.retnakaran@nutanix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).