Het Gala <het.gala@nutanix.com> writes:
On 06/03/24 8:06 pm, Fabiano Rosas wrote:
Het Gala<het.gala@nutanix.com> writes:
Add a migrate_set_ports() function that from each QDict, fills in
the port in case it was 0 in the test.
Handle a list of channels so we can add a negative test that
passes more than one channel.
Signed-off-by: Het Gala<het.gala@nutanix.com>
Suggested-by: Fabiano Rosas<farosas@suse.de>
---
tests/qtest/migration-helpers.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/tests/qtest/migration-helpers.c b/tests/qtest/migration-helpers.c
index 478c1f259b..df4978bf17 100644
--- a/tests/qtest/migration-helpers.c
+++ b/tests/qtest/migration-helpers.c
@@ -17,6 +17,8 @@
#include "qapi/qapi-visit-sockets.h"
#include "qapi/qobject-input-visitor.h"
#include "qapi/error.h"
+#include "qapi/qmp/qlist.h"
+
Extra line here. This is unwanted because it sometimes trips git into
thinking there's a conflict here when another patch changes the
surrounding lines.
Ack, that makes sense
#include "migration-helpers.h"
@@ -73,6 +75,29 @@ migrate_get_socket_address(QTestState *who, const char *parameter)
return result;
}
+static void migrate_set_ports(QTestState *to, QList *channelList)
+{
+ g_autofree char *addr = NULL;
+ g_autofree char *addr_port = NULL;
+ QListEntry *entry;
+
+ addr = migrate_get_socket_address(to, "socket-address");
+ addr_port = g_strsplit(addr, ":", 3)[2];
Will this always do the right thing when the src/dst use different types
of channels? If there is some kind of mismatch (say one side uses vsock
and the other inet), it's better that this function doesn't touch the
channels dict instead of putting garbage in the port field.
Yes you are right. This will fail if there is a mismatch in type of
channels.
Better idea would be to check if 'port' key is present in both, i.e. in
'addr'
as well as 'addrdict' and only then change the port ?
Yep, either parse the type from string or add a version of
migrate_get_socket_address that returns a dict. Then check if type
matches and port exists.
Also what happens if the dst is using unix: or fd:?
yes in that case - how should the migration behaviour be ? src and dst
should be of the same type right
Remember this is test code. If the test was written incorrectly either
by developer mistake or on purpose to test some condition, then it's not
this function's reponsibility to fix that.
Replace the port only if the transport type allows for a port, there is
a port in both addr and addrdict and port is 0. Anything else, leave the
channelList untouched and let QEMU deal with the bad input.
+
+ QLIST_FOREACH_ENTRY(channelList, entry) {
+ QDict *channel = qobject_to(QDict, qlist_entry_obj(entry));
+ QObject *addr_obj = qdict_get(channel, "addr");
+
+ if (qobject_type(addr_obj) == QTYPE_QDICT) {
+ QDict *addrdict = qobject_to(QDict, addr_obj);
You might not need these two lines if at the start you use:
QDict *addr = qdict_get_dict(channel, "addr");
If you are commenting regarding this two lines:
+ if (qobject_type(addr_obj) == QTYPE_QDICT) {
+ QDict *addrdict = qobject_to(QDict, addr_obj);
then, I am not sure, because addrdict and addr is different right? Also
addrdict can also
be a QList, like in the case of exec migration, it can be a list instead of dict
ex:
# -> { "execute": "migrate",
# "arguments": {
# "channels": [ { "channel-type": "main",
# "addr": { "transport": "exec",
# "args": [ "/bin/nc", "-p", "6000",
# "/some/sock" ] } } ] } }
"addr" is always a dict, no? Even in the example you just gave.
+ if (qdict_haskey(addrdict, "port") &&
+ (strcmp(qdict_get_str(addrdict, "port"), "0") == 0)) {
+ qdict_put_str(addrdict, "port", addr_port);
+ }
+ }
+ }
+}
+
bool migrate_watch_for_events(QTestState *who, const char *name,
QDict *event, void *opaque)
{
@@ -143,6 +168,7 @@ void migrate_qmp(QTestState *who, QTestState *to, const
char *uri,
if (!uri) {
connect_uri = migrate_get_socket_address(to, "socket-address");
}
+ migrate_set_ports(to, NULL);
migrate_set_ports is not prepared to take NULL. This breaks the tests in
this commit. All individual commits should work, otherwise it will break
bisecting.
Okay, so in that case, is it better to merge this with the next patch ?
because if I just
define the migrate_set_ports function and not use it anywhere, it gives
a warning/error
(depending upon what compiler is used)
You can return early at migrate_set_ports if channelList is NULL.
Also, I just noticed: s/channelList/channel_list/