From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 3/3] Add connection tests for bind()
Date: Fri, 20 Mar 2020 09:54:27 +0100 [thread overview]
Message-ID: <20200320085427.GA14750@dell5510> (raw)
In-Reply-To: <20200317121057.13529-3-mdoucha@suse.cz>
Hi Martin,
whole patchset is very nice work. Thanks!
> +static void setup(void)
> +{
> + srand(time(0));
> +
> + tst_init_sockaddr_inet(&ipv4_addr, IPV4_ADDRESS, 0);
> + tst_init_sockaddr_inet_bin(&ipv4_any_addr, INADDR_ANY, 0);
> + tst_init_sockaddr_inet6_bin(&ipv6_addr, &in6addr_loopback, 0);
> + tst_init_sockaddr_inet6_bin(&ipv6_any_addr, &in6addr_any, 0);
> +}
You don't use tst_init_sockaddr_inet6() at all. How about using it?
Or do you have some reason not to use it?
Kind regards,
Petr
diff --git testcases/kernel/syscalls/bind/bind04.c testcases/kernel/syscalls/bind/bind04.c
index 1be14560b..cdd4f38f5 100644
--- testcases/kernel/syscalls/bind/bind04.c
+++ testcases/kernel/syscalls/bind/bind04.c
@@ -77,7 +77,7 @@ static void setup(void)
tst_init_sockaddr_inet(&ipv4_addr, IPV4_ADDRESS, 0);
tst_init_sockaddr_inet_bin(&ipv4_any_addr, INADDR_ANY, 0);
- tst_init_sockaddr_inet6_bin(&ipv6_addr, &in6addr_loopback, 0);
+ tst_init_sockaddr_inet6(&ipv6_addr, IPV6_ADDRESS, 0);
tst_init_sockaddr_inet6_bin(&ipv6_any_addr, &in6addr_any, 0);
}
diff --git testcases/kernel/syscalls/bind/bind05.c testcases/kernel/syscalls/bind/bind05.c
index 16c9c711d..fdab8b22e 100644
--- testcases/kernel/syscalls/bind/bind05.c
+++ testcases/kernel/syscalls/bind/bind05.c
@@ -77,7 +77,7 @@ static void setup(void)
tst_init_sockaddr_inet(&ipv4_addr, IPV4_ADDRESS, 0);
tst_init_sockaddr_inet_bin(&ipv4_any_addr, INADDR_ANY, 0);
- tst_init_sockaddr_inet6_bin(&ipv6_addr, &in6addr_loopback, 0);
+ tst_init_sockaddr_inet6(&ipv6_addr, IPV6_ADDRESS, 0);
tst_init_sockaddr_inet6_bin(&ipv6_any_addr, &in6addr_any, 0);
}
next prev parent reply other threads:[~2020-03-20 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 12:10 [LTP] [PATCH v4 1/3] Create separate .c file for include/tst_net.h Martin Doucha
2020-03-17 12:10 ` [LTP] [PATCH v4 2/3] Add socket address initialization functions to tst_net library Martin Doucha
2020-03-20 9:03 ` Petr Vorel
2020-03-20 9:44 ` Martin Doucha
2020-03-20 9:22 ` Petr Vorel
2020-03-17 12:10 ` [LTP] [PATCH v4 3/3] Add connection tests for bind() Martin Doucha
2020-03-20 8:54 ` Petr Vorel [this message]
2020-03-20 9:43 ` Martin Doucha
2020-03-20 11:18 ` Petr Vorel
2020-03-20 9:53 ` Petr Vorel
2020-03-17 20:03 ` [LTP] [PATCH v4 1/3] Create separate .c file for include/tst_net.h Petr Vorel
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=20200320085427.GA14750@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.