From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PULL 03/11] test-util-sockets: Clean up SocketAddress construction
Date: Tue, 3 Nov 2020 14:02:17 +0000 [thread overview]
Message-ID: <20201103140225.496776-4-berrange@redhat.com> (raw)
In-Reply-To: <20201103140225.496776-1-berrange@redhat.com>
From: Markus Armbruster <armbru@redhat.com>
The thread functions build the SocketAddress from global variable
@abstract_sock_name and the tight flag passed as pointer
argument (either NULL or (gpointer)1). There is no need for such
hackery; simply pass the SocketAddress instead.
While there, dumb down g_rand_int_range() to g_random_int().
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>
---
tests/test-util-sockets.c | 64 ++++++++++++++++-----------------------
1 file changed, 26 insertions(+), 38 deletions(-)
diff --git a/tests/test-util-sockets.c b/tests/test-util-sockets.c
index 9d317e73a6..a4792253ba 100644
--- a/tests/test-util-sockets.c
+++ b/tests/test-util-sockets.c
@@ -230,25 +230,15 @@ static void test_socket_fd_pass_num_nocli(void)
#endif
#ifdef __linux__
-static gchar *abstract_sock_name;
-
static gpointer unix_server_thread_func(gpointer user_data)
{
- SocketAddress addr;
- Error *err = NULL;
- int fd = -1;
- int connfd = -1;
+ SocketAddress *addr = user_data;
+ int fd;
+ int connfd;
struct sockaddr_un un;
socklen_t len = sizeof(un);
- 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);
+ fd = socket_listen(addr, 1, &error_abort);
g_assert_cmpint(fd, >=, 0);
g_assert(fd_is_socket(fd));
@@ -257,69 +247,67 @@ static gpointer unix_server_thread_func(gpointer user_data)
close(connfd);
close(fd);
-
return NULL;
}
static gpointer unix_client_thread_func(gpointer user_data)
{
- SocketAddress addr;
- Error *err = NULL;
- int fd = -1;
-
- 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);
+ SocketAddress *addr = user_data;
+ int fd;
+ fd = socket_connect(addr, &error_abort);
g_assert_cmpint(fd, >=, 0);
-
close(fd);
-
return NULL;
}
static void test_socket_unix_abstract_good(void)
{
- GRand *r = g_rand_new();
+ SocketAddress addr;
- abstract_sock_name = g_strdup_printf("unix-%d-%d", getpid(),
- g_rand_int_range(r, 100, 1000));
+ addr.type = SOCKET_ADDRESS_TYPE_UNIX;
+ addr.u.q_unix.path = g_strdup_printf("unix-%d-%u",
+ getpid(), g_random_int());
+ addr.u.q_unix.has_abstract = true;
+ addr.u.q_unix.abstract = true;
/* non tight socklen serv and cli */
+
+ addr.u.q_unix.has_tight = false;
+ addr.u.q_unix.tight = false;
+
GThread *serv = g_thread_new("abstract_unix_server",
unix_server_thread_func,
- NULL);
+ &addr);
sleep(1);
GThread *cli = g_thread_new("abstract_unix_client",
unix_client_thread_func,
- NULL);
+ &addr);
g_thread_join(cli);
g_thread_join(serv);
/* tight socklen serv and cli */
+
+ addr.u.q_unix.has_tight = true;
+ addr.u.q_unix.tight = true;
+
serv = g_thread_new("abstract_unix_server",
unix_server_thread_func,
- (gpointer)1);
+ &addr);
sleep(1);
cli = g_thread_new("abstract_unix_client",
unix_client_thread_func,
- (gpointer)1);
+ &addr);
g_thread_join(cli);
g_thread_join(serv);
- g_free(abstract_sock_name);
- g_rand_free(r);
+ g_free(addr.u.q_unix.path);
}
#endif
--
2.28.0
next prev parent reply other threads:[~2020-11-03 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 14:02 [PULL 00/11] Sock next patches Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 01/11] test-util-sockets: Plug file descriptor leak Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 02/11] test-util-sockets: Correct to set has_abstract, has_tight Daniel P. Berrangé
2020-11-03 14:02 ` Daniel P. Berrangé [this message]
2020-11-03 14:02 ` [PULL 04/11] test-util-sockets: Factor out test_socket_unix_abstract_one() Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 05/11] test-util-sockets: Synchronize properly, don't sleep(1) Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 06/11] test-util-sockets: Test the complete abstract socket matrix Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 07/11] sockets: Fix default of UnixSocketAddress member @tight Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 08/11] sockets: Fix socket_sockaddr_to_address_unix() for abstract sockets Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 09/11] char-socket: Fix qemu_chr_socket_address() " Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 10/11] sockets: Bypass "replace empty @path" for abstract unix sockets Daniel P. Berrangé
2020-11-03 14:02 ` [PULL 11/11] sockets: Make abstract UnixSocketAddress depend on CONFIG_LINUX Daniel P. Berrangé
2020-11-03 15:35 ` [PULL 00/11] Sock next patches Peter Maydell
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=20201103140225.496776-4-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).