Thread (24 messages) 24 messages, 4 authors, 2025-01-28

Re: [PATCH net v2 3/6] vsock/test: Introduce vsock_bind()

From: Stefano Garzarella <sgarzare@redhat.com>
Date: 2025-01-23 11:07:26

On Thu, Jan 23, 2025 at 12:02:36PM +0100, Luigi Leonardi wrote:
On Wed, Jan 22, 2025 at 09:11:30PM +0100, Michal Luczaj wrote:
quoted
On 1/22/25 17:01, Luigi Leonardi wrote:
quoted
On Tue, Jan 21, 2025 at 03:44:04PM +0100, Michal Luczaj wrote:
quoted
Add a helper for socket()+bind(). Adapt callers.

Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Signed-off-by: Michal Luczaj <redacted>
---
tools/testing/vsock/util.c       | 56 +++++++++++++++++-----------------------
tools/testing/vsock/util.h       |  1 +
tools/testing/vsock/vsock_test.c | 17 +-----------
3 files changed, 25 insertions(+), 49 deletions(-)
diff --git a/tools/testing/vsock/util.c b/tools/testing/vsock/util.c
index 34e9dac0a105f8aeb8c9af379b080d5ce8cb2782..31ee1767c8b73c05cfd219c3d520a677df6e66a6 100644
--- a/tools/testing/vsock/util.c
+++ b/tools/testing/vsock/util.c
@@ -96,33 +96,42 @@ void vsock_wait_remote_close(int fd)
close(epollfd);
}

-/* Bind to <bind_port>, connect to <cid, port> and return the file descriptor. */
-int vsock_bind_connect(unsigned int cid, unsigned int port, unsigned int bind_port, int type)
If you need to send a v3, it would be nice to have a comment for
vsock_bind, as there used to be one.
Comment for vsock_bind_connect() remains, see below. As for vsock_bind(),
perhaps it's time to start using kernel-doc comments?
This is a good idea! @Stefano WDYT?
I'm not sure it's worth it since they are just tests, but if someone
wants to do it, absolutely no objection.

Thanks,
Stefano
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help