test-util-sockets: Correct to set has_abstract, has_tight

The code tested doesn't care, which is a bug I will fix shortly.

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Markus Armbruster 2020-11-02 10:44:13 +01:00 committed by Daniel P. Berrangé
parent 9ce22da0d8
commit d1a393211b

View file

@ -243,7 +243,9 @@ static gpointer unix_server_thread_func(gpointer user_data)
addr.type = SOCKET_ADDRESS_TYPE_UNIX;
addr.u.q_unix.path = abstract_sock_name;
addr.u.q_unix.has_tight = true;
addr.u.q_unix.tight = user_data != NULL;
addr.u.q_unix.has_abstract = true;
addr.u.q_unix.abstract = true;
fd = socket_listen(&addr, 1, &err);
@ -267,7 +269,9 @@ static gpointer unix_client_thread_func(gpointer user_data)
addr.type = SOCKET_ADDRESS_TYPE_UNIX;
addr.u.q_unix.path = abstract_sock_name;
addr.u.q_unix.has_tight = true;
addr.u.q_unix.tight = user_data != NULL;
addr.u.q_unix.has_abstract = true;
addr.u.q_unix.abstract = true;
fd = socket_connect(&addr, &err);