From: Felipe Franciosi <felipe@nutanix.com>
To: berrange@redhat.com, marcandre.lureau@redhat.com
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
Felipe Franciosi <felipe@nutanix.com>
Subject: [Qemu-devel] [PATCH v3 4/4] io: Add a QIOChannelSocket cleanup test
Date: Thu, 29 Sep 2016 08:52:38 -0700 [thread overview]
Message-ID: <1475164358-2933-5-git-send-email-felipe@nutanix.com> (raw)
In-Reply-To: <1475164358-2933-1-git-send-email-felipe@nutanix.com>
This patch adds a test to verify that the QIOChannel framework will not
unlink a filesystem unix socket unless the _FEATURE_LISTEN bit is set.
Due to a bug introduced in 74b6ce43, the framework would unlink the
entry if the _FEATURE_SHUTDOWN bit was set, regardless of the presence
of _FEATURE_LISTEN.
Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
---
tests/test-io-channel-socket.c | 33 +++++++++++++++++++++++++++++++++
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/tests/test-io-channel-socket.c b/tests/test-io-channel-socket.c
index f73e063..aa88c3c 100644
--- a/tests/test-io-channel-socket.c
+++ b/tests/test-io-channel-socket.c
@@ -491,6 +491,37 @@ static void test_io_channel_unix_fd_pass(void)
}
g_free(fdrecv);
}
+
+static void test_io_channel_unix_listen_cleanup(void)
+{
+ QIOChannelSocket *ioc;
+ struct sockaddr_un un;
+ int sock;
+
+#define TEST_SOCKET "test-io-channel-socket.sock"
+
+ ioc = qio_channel_socket_new();
+
+ /* Manually bind ioc without calling the qio api to avoid setting
+ * the LISTEN feature */
+ sock = qemu_socket(PF_UNIX, SOCK_STREAM, 0);
+ memset(&un, 0, sizeof(un));
+ un.sun_family = AF_UNIX;
+ snprintf(un.sun_path, sizeof(un.sun_path), "%s", TEST_SOCKET);
+ unlink(TEST_SOCKET);
+ bind(sock, (struct sockaddr *)&un, sizeof(un));
+ ioc->fd = sock;
+ ioc->localAddrLen = sizeof(ioc->localAddr);
+ getsockname(sock, (struct sockaddr *)&ioc->localAddr,
+ &ioc->localAddrLen);
+
+ g_assert(g_file_test(TEST_SOCKET, G_FILE_TEST_EXISTS));
+ object_unref(OBJECT(ioc));
+ g_assert(g_file_test(TEST_SOCKET, G_FILE_TEST_EXISTS));
+
+ unlink(TEST_SOCKET);
+}
+
#endif /* _WIN32 */
@@ -562,6 +593,8 @@ int main(int argc, char **argv)
test_io_channel_unix_async);
g_test_add_func("/io/channel/socket/unix-fd-pass",
test_io_channel_unix_fd_pass);
+ g_test_add_func("/io/channel/socket/unix-listen-cleanup",
+ test_io_channel_unix_listen_cleanup);
#endif /* _WIN32 */
return g_test_run();
--
1.7.1
next prev parent reply other threads:[~2016-09-29 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 15:52 [Qemu-devel] [PATCH v3 0/4] io: Various fixes around QIOChannel Features Felipe Franciosi
2016-09-29 15:52 ` [Qemu-devel] [PATCH v3 1/4] io: Fix double shift usages on QIOChannel features Felipe Franciosi
2016-09-29 15:52 ` [Qemu-devel] [PATCH v3 2/4] io: Use qio_channel_has_feature() where applicable Felipe Franciosi
2016-09-29 15:52 ` [Qemu-devel] [PATCH v3 3/4] io: Introduce a qio_channel_set_feature() helper Felipe Franciosi
2016-09-29 15:52 ` Felipe Franciosi [this message]
2016-09-29 16:32 ` [Qemu-devel] [PATCH v3 0/4] io: Various fixes around QIOChannel Features Daniel P. Berrange
2016-10-01 15:33 ` Felipe Franciosi
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=1475164358-2933-5-git-send-email-felipe@nutanix.com \
--to=felipe@nutanix.com \
--cc=berrange@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).