* [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter
@ 2018-07-19 12:53 Petr Vorel
2018-07-19 12:53 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
2018-07-26 7:45 ` [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
0 siblings, 2 replies; 8+ messages in thread
From: Petr Vorel @ 2018-07-19 12:53 UTC (permalink / raw)
To: ltp
Helps to find typo errors.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
testcases/network/netstress/netstress.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/testcases/network/netstress/netstress.c b/testcases/network/netstress/netstress.c
index 17e401eb0..48fb0aabd 100644
--- a/testcases/network/netstress/netstress.c
+++ b/testcases/network/netstress/netstress.c
@@ -837,6 +837,8 @@ static void set_protocol_type(void)
proto_type = TYPE_DCCP;
else if (!strcmp(type, "sctp"))
proto_type = TYPE_SCTP;
+ else
+ tst_brk(TCONF, "wrong proto_type: '%s'", type);
}
static void setup(void)
--
2.18.0
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-07-19 12:53 [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
@ 2018-07-19 12:53 ` Petr Vorel
2018-07-23 6:22 ` Alexey Kodanev
2018-07-24 14:14 ` Petr Vorel
2018-07-26 7:45 ` [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
1 sibling, 2 replies; 8+ messages in thread
From: Petr Vorel @ 2018-07-19 12:53 UTC (permalink / raw)
To: ltp
For udp, udp_lite and DCCP on client is timeout set 100.
For udp and udp_lite on server on low timeout it reaches "recv failed"
error (due no listen in udp and udp_lite).
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
I documented the current state, but I it looks to me that udp and
udp_lite on server is a bug. Or wanted behaviour?
Kind regards,
Petr
---
testcases/network/netstress/netstress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testcases/network/netstress/netstress.c b/testcases/network/netstress/netstress.c
index 48fb0aabd..62301ca9f 100644
--- a/testcases/network/netstress/netstress.c
+++ b/testcases/network/netstress/netstress.c
@@ -999,7 +999,7 @@ static struct tst_option options[] = {
{"r:", &rarg, "-r x Number of client requests"},
{"n:", &narg, "-n x Client message size"},
{"N:", &Narg, "-N x Server message size"},
- {"m:", &Targ, "-m x Reply timeout in microsec."},
+ {"m:", &Targ, "-m x Reply timeout in microsec (only for tcp and sctp, also affects server on udp and udp_lite)."},
{"d:", &rpath, "-d x x is a path to file where result is saved"},
{"A:", &Aarg, "-A x x max payload length (generated randomly)\n"},
--
2.18.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-07-19 12:53 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
@ 2018-07-23 6:22 ` Alexey Kodanev
2018-07-24 14:14 ` Petr Vorel
1 sibling, 0 replies; 8+ messages in thread
From: Alexey Kodanev @ 2018-07-23 6:22 UTC (permalink / raw)
To: ltp
On 19.07.2018 15:53, Petr Vorel wrote:
> For udp, udp_lite and DCCP on client is timeout set 100.
> For udp and udp_lite on server on low timeout it reaches "recv failed"
> error (due no listen in udp and udp_lite).
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> I documented the current state, but I it looks to me that udp and
> udp_lite on server is a bug. Or wanted behaviour?
>
>
Hi Petr,
Since the server waits for requests from the client, the timeout
value for UDP/DCCP is the same as for the other protocols. Also the
server starts earlier than the client, so it should wait some time
to get the client requests.
I've changed the client side only because either request from the
client or reply from the server might be lost.
> Kind regards,
> Petr
> ---
> testcases/network/netstress/netstress.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testcases/network/netstress/netstress.c b/testcases/network/netstress/netstress.c
> index 48fb0aabd..62301ca9f 100644
> --- a/testcases/network/netstress/netstress.c
> +++ b/testcases/network/netstress/netstress.c
> @@ -999,7 +999,7 @@ static struct tst_option options[] = {
> {"r:", &rarg, "-r x Number of client requests"},
> {"n:", &narg, "-n x Client message size"},
> {"N:", &Narg, "-N x Server message size"},
> - {"m:", &Targ, "-m x Reply timeout in microsec."},
> + {"m:", &Targ, "-m x Reply timeout in microsec (only for tcp and sctp, also affects server on udp and udp_lite)."},
What about dccp? May be "Receive timeout in milliseconds (not affects UDP/DCCP client)"?
Thanks,
Alexey
^ permalink raw reply [flat|nested] 8+ messages in thread* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-07-19 12:53 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
2018-07-23 6:22 ` Alexey Kodanev
@ 2018-07-24 14:14 ` Petr Vorel
2018-07-27 10:24 ` Alexey Kodanev
1 sibling, 1 reply; 8+ messages in thread
From: Petr Vorel @ 2018-07-24 14:14 UTC (permalink / raw)
To: ltp
Hi Alexey,
> Hi Petr,
> Since the server waits for requests from the client, the timeout
> value for UDP/DCCP is the same as for the other protocols. Also the
> server starts earlier than the client, so it should wait some time
> to get the client requests.
> I've changed the client side only because either request from the
> client or reply from the server might be lost.
Thanks for your explanation.
I mean: UDP itself is the only protocol which don't support listen() so
netstress server using UDP timeouts after some time. The default is 100ms.
But due obvious return before listen() for UDP in server_init() -m parameter
affects behavior of the server in UDP (how quickly it timeouts):
$ date +"%T.%3N"; testcases/network/netstress/netstress -m 1 -T udp; date +"%T.%3N"
15:52:34.501
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
netstress.c:917: INFO: max requests '3'
netstress.c:944: INFO: using UDP
netstress.c:676: INFO: assigning a name to the server socket...
netstress.c:683: INFO: bind to port 47728
netstress.c:575: FAIL: recv failed, sock '3'
netstress.c:642: BROK: Server closed
...
15:52:34.516
$ date +"%T.%3N"; testcases/network/netstress/netstress -m 1000 -T udp; date +"%T.%3N"
16:01:27.064
...
16:01:28.079
date +"%T.%3N"; testcases/network/netstress/netstress -m 10000 -T udp; date +"%T.%3N"
16:00:39.647
...
16:00:49.672
I just wonder if we want to document it (or at least don't state -m as "client only config").
> > - {"m:", &Targ, "-m x Reply timeout in microsec."},
> > + {"m:", &Targ, "-m x Reply timeout in microsec (only for tcp and sctp, also affects server on udp and udp_lite)."},
> What about dccp?
Yes, I left it, thanks!
> May be "Receive timeout in milliseconds (not affects UDP/DCCP client)"?
Yes, this is better.
Kind regards,
Petr
^ permalink raw reply [flat|nested] 8+ messages in thread* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-07-24 14:14 ` Petr Vorel
@ 2018-07-27 10:24 ` Alexey Kodanev
0 siblings, 0 replies; 8+ messages in thread
From: Alexey Kodanev @ 2018-07-27 10:24 UTC (permalink / raw)
To: ltp
On 07/24/2018 05:14 PM, Petr Vorel wrote:
> Hi Alexey,
>
>> Hi Petr,
>
>> Since the server waits for requests from the client, the timeout
>> value for UDP/DCCP is the same as for the other protocols. Also the
>> server starts earlier than the client, so it should wait some time
>> to get the client requests.
>
>> I've changed the client side only because either request from the
>> client or reply from the server might be lost.
>
> Thanks for your explanation.
> I mean: UDP itself is the only protocol which don't support listen() so
> netstress server using UDP timeouts after some time. The default is 100ms.
Hmm, for the server the default should be 60 sec. Does it timeout earlier?
It is more than enough for the tests to start the client on the other end
and start sending requests. If it hasn't happened during this time period
there is no reason to have it running there.
> But due obvious return before listen() for UDP in server_init() -m parameter
> affects behavior of the server in UDP (how quickly it timeouts):
>
And with listen() it won't wait forever either, it will be killed by LTP
timeout per test run...
> $ date +"%T.%3N"; testcases/network/netstress/netstress -m 1 -T udp; date +"%T.%3N"
> 15:52:34.501
> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
> netstress.c:917: INFO: max requests '3'
> netstress.c:944: INFO: using UDP
> netstress.c:676: INFO: assigning a name to the server socket...
> netstress.c:683: INFO: bind to port 47728
> netstress.c:575: FAIL: recv failed, sock '3'
> netstress.c:642: BROK: Server closed
> ...
> 15:52:34.516
Thanks,
Alexey
^ permalink raw reply [flat|nested] 8+ messages in thread
* [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter
2018-07-19 12:53 [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
2018-07-19 12:53 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
@ 2018-07-26 7:45 ` Petr Vorel
1 sibling, 0 replies; 8+ messages in thread
From: Petr Vorel @ 2018-07-26 7:45 UTC (permalink / raw)
To: ltp
Hi,
> Helps to find typo errors.
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> testcases/network/netstress/netstress.c | 2 ++
> 1 file changed, 2 insertions(+)
> diff --git a/testcases/network/netstress/netstress.c b/testcases/network/netstress/netstress.c
> index 17e401eb0..48fb0aabd 100644
> --- a/testcases/network/netstress/netstress.c
> +++ b/testcases/network/netstress/netstress.c
> @@ -837,6 +837,8 @@ static void set_protocol_type(void)
> proto_type = TYPE_DCCP;
> else if (!strcmp(type, "sctp"))
> proto_type = TYPE_SCTP;
> + else
> + tst_brk(TCONF, "wrong proto_type: '%s'", type);
Pushed with minor change:
Using TBROK to be consistent with error messages in setup():
tst_brk(TBROK, "Invalid proto_type: '%s'", type);
Kind regards,
Petr
^ permalink raw reply [flat|nested] 8+ messages in thread
* [LTP] [PATCH RFC 1/4] lib/tst_test.c: add 'needs_drivers' option with tst_check_drivers cmd
@ 2018-08-09 15:23 Alexey Kodanev
2018-08-09 15:23 ` [LTP] [PATCH RFC 4/4] network/ipsec: replace ipsec_try() with TST_RTNL_CHK() Alexey Kodanev
0 siblings, 1 reply; 8+ messages in thread
From: Alexey Kodanev @ 2018-08-09 15:23 UTC (permalink / raw)
To: ltp
The drivers are checked with modprobe. If modrpobe is not available
on the system, the checks are silently skipped.
Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
---
include/tst_test.h | 5 +++++
lib/tst_test.c | 26 ++++++++++++++++++++++++++
testcases/lib/.gitignore | 1 +
testcases/lib/Makefile | 2 +-
testcases/lib/tst_check_drivers.c | 24 ++++++++++++++++++++++++
5 files changed, 57 insertions(+), 1 deletions(-)
create mode 100644 testcases/lib/tst_check_drivers.c
diff --git a/include/tst_test.h b/include/tst_test.h
index 98dacf3..221796d 100644
--- a/include/tst_test.h
+++ b/include/tst_test.h
@@ -170,6 +170,9 @@ struct tst_test {
/* NULL terminated array of resource file names */
const char *const *resource_files;
+
+ /* NULL terminated array of needed kernel drivers */
+ const char * const *needs_drivers;
};
/*
@@ -219,6 +222,8 @@ const char *tst_strstatus(int status);
void tst_set_timeout(int timeout);
+int tst_check_drivers(void);
+
#ifndef TST_NO_DEFAULT_MAIN
static struct tst_test test;
diff --git a/lib/tst_test.c b/lib/tst_test.c
index 2f3d357..6cb74cf 100644
--- a/lib/tst_test.c
+++ b/lib/tst_test.c
@@ -645,6 +645,29 @@ static int needs_tmpdir(void)
tst_test->needs_checkpoints;
}
+int tst_check_drivers(void)
+{
+ const char *name;
+ int i, res;
+
+ for (i = 0; (name = tst_test->needs_drivers[i]); ++i) {
+ const char * const argv[] = { "modprobe", name, NULL };
+
+ res = tst_run_cmd_(NULL, argv, "/dev/null", "/dev/null", 1);
+ if (res == 255)
+ return res; /* it looks like modprobe not available */
+ if (res) {
+ if (tst_test->test || tst_test->test_all) {
+ tst_brk(TCONF, "%s driver not available", name);
+ } else {
+ fprintf(stderr, "%s", name);
+ return res;
+ }
+ }
+ }
+ return 0;
+}
+
static void copy_resources(void)
{
unsigned int i;
@@ -767,6 +790,9 @@ static void do_setup(int argc, char *argv[])
if (tst_test->min_kver)
check_kver();
+ if (tst_test->needs_drivers)
+ tst_check_drivers();
+
if (tst_test->format_device)
tst_test->needs_device = 1;
diff --git a/testcases/lib/.gitignore b/testcases/lib/.gitignore
index a9034e4..d83a48e 100644
--- a/testcases/lib/.gitignore
+++ b/testcases/lib/.gitignore
@@ -1,5 +1,6 @@
/tst_sleep
/tst_random
+/tst_check_drivers
/tst_checkpoint
/tst_rod
/tst_kvcmp
diff --git a/testcases/lib/Makefile b/testcases/lib/Makefile
index 3547e16..e1dea3b 100644
--- a/testcases/lib/Makefile
+++ b/testcases/lib/Makefile
@@ -28,6 +28,6 @@ INSTALL_TARGETS := *.sh
MAKE_TARGETS := tst_sleep tst_random tst_checkpoint tst_rod tst_kvcmp\
tst_device tst_net_iface_prefix tst_net_ip_prefix tst_net_vars\
- tst_getconf tst_supported_fs
+ tst_getconf tst_supported_fs tst_check_drivers
include $(top_srcdir)/include/mk/generic_leaf_target.mk
diff --git a/testcases/lib/tst_check_drivers.c b/testcases/lib/tst_check_drivers.c
new file mode 100644
index 0000000..3f722f2
--- /dev/null
+++ b/testcases/lib/tst_check_drivers.c
@@ -0,0 +1,24 @@
+/* SPDX-License-Identifier: GPL-2.0-or-later
+ * Copyright (c) 2018 Oracle and/or its affiliates. All Rights Reserved.
+ */
+
+#include <stdio.h>
+#define TST_NO_DEFAULT_MAIN
+#include "tst_test.h"
+
+struct tst_test *tst_test;
+
+int main(int argc, const char *argv[])
+{
+ if (argc < 2) {
+ fprintf(stderr, "Please provide kernel driver list\n");
+ return 1;
+ }
+
+ struct tst_test test = {
+ .needs_drivers = &argv[1]
+ };
+
+ tst_test = &test;
+ return tst_check_drivers();
+}
--
1.7.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* [LTP] [PATCH RFC 4/4] network/ipsec: replace ipsec_try() with TST_RTNL_CHK()
2018-08-09 15:23 [LTP] [PATCH RFC 1/4] lib/tst_test.c: add 'needs_drivers' option with tst_check_drivers cmd Alexey Kodanev
@ 2018-08-09 15:23 ` Alexey Kodanev
2018-08-16 11:16 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
0 siblings, 1 reply; 8+ messages in thread
From: Alexey Kodanev @ 2018-08-09 15:23 UTC (permalink / raw)
To: ltp
Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
---
testcases/network/stress/ipsec/ipsec_lib.sh | 21 +++------------------
1 files changed, 3 insertions(+), 18 deletions(-)
diff --git a/testcases/network/stress/ipsec/ipsec_lib.sh b/testcases/network/stress/ipsec/ipsec_lib.sh
index aedba9b..f850166 100644
--- a/testcases/network/stress/ipsec/ipsec_lib.sh
+++ b/testcases/network/stress/ipsec/ipsec_lib.sh
@@ -157,21 +157,6 @@ ipsec_set_algoline()
esac
}
-ipsec_try()
-{
- local output="$($@ 2>&1 || echo 'TERR')"
-
- if echo "$output" | grep -q "TERR"; then
- echo "$output" | grep -q \
- 'RTNETLINK answers: Function not implemented' && \
- tst_brk TCONF "'$@': not implemented"
- echo "$output" | grep -q \
- 'RTNETLINK answers: Operation not supported' && \
- tst_brk TCONF "'$@': not supported (maybe missing 'ip${TST_IPV6}_vti' kernel module)"
- tst_brk TBROK "$@ failed: $output"
- fi
-}
-
# tst_ipsec target src_addr dst_addr: config ipsec
#
# target: target of the configuration host ( lhost / rhost )
@@ -195,7 +180,7 @@ tst_ipsec()
if [ $target = lhost ]; then
local spi_1="0x$SPI"
local spi_2="0x$(( $SPI + 1 ))"
- ipsec_try ip xfrm state add src $src dst $dst spi $spi_1 \
+ TST_RTNL_CHK xfrm state add src $src dst $dst spi $spi_1 \
$p $ALG mode $mode sel src $src dst $dst
ROD ip xfrm state add src $dst dst $src spi $spi_2 \
$p $ALG mode $mode sel src $dst dst $src
@@ -257,12 +242,12 @@ tst_ipsec_vti()
cleanup_vti=$vti
if [ $target = lhost ]; then
- ipsec_try ip li add $vti $type local $src remote $dst $key $d
+ TST_RTNL_CHK ip li add $vti $type local $src remote $dst $key $d
ROD ip li set $vti up
local spi_1="spi 0x$SPI"
local spi_2="spi 0x$(( $SPI + 1 ))"
- ipsec_try $ipx st add $o_dir $p $spi_1 $ALG $m
+ TST_RTNL_CHK $ipx st add $o_dir $p $spi_1 $ALG $m
ROD $ipx st add $i_dir $p $spi_2 $ALG $m
ROD $ipx po add dir out tmpl $o_dir $p $m $mrk
ROD $ipx po add dir in tmpl $i_dir $p $m $mrk
--
1.7.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-08-09 15:23 ` [LTP] [PATCH RFC 4/4] network/ipsec: replace ipsec_try() with TST_RTNL_CHK() Alexey Kodanev
@ 2018-08-16 11:16 ` Petr Vorel
2018-08-16 12:01 ` Alexey Kodanev
0 siblings, 1 reply; 8+ messages in thread
From: Petr Vorel @ 2018-08-16 11:16 UTC (permalink / raw)
To: ltp
Hi Alexey,
> >> Hi Petr,
> >> Since the server waits for requests from the client, the timeout
> >> value for UDP/DCCP is the same as for the other protocols. Also the
> >> server starts earlier than the client, so it should wait some time
> >> to get the client requests.
> >> I've changed the client side only because either request from the
> >> client or reply from the server might be lost.
> > Thanks for your explanation.
> > I mean: UDP itself is the only protocol which don't support listen() so
> > netstress server using UDP timeouts after some time. The default is 100ms.
> Hmm, for the server the default should be 60 sec. Does it timeout earlier?
Yes. The timeout is affected by value of -m. Thats' what I meant by my previous:
$ date +"%T.%3N"; testcases/network/netstress/netstress -m 1 -T udp; date +"%T.%3N"
15:52:34.501
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
The timeout is actually 1ms. Try it with -m 1000 and it'll be indeed 1s
netstress.c:917: INFO: max requests '3'
netstress.c:944: INFO: using UDP
netstress.c:676: INFO: assigning a name to the server socket...
netstress.c:683: INFO: bind to port 47728
netstress.c:575: FAIL: recv failed, sock '3'
netstress.c:642: BROK: Server closed
...
15:52:34.516
This is caused by udp/udp_lite not using listen(), but maybe is should be at
least mentioned in help (if wanted behavior).
Kind regards,
Petr
^ permalink raw reply [flat|nested] 8+ messages in thread
* [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior
2018-08-16 11:16 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
@ 2018-08-16 12:01 ` Alexey Kodanev
0 siblings, 0 replies; 8+ messages in thread
From: Alexey Kodanev @ 2018-08-16 12:01 UTC (permalink / raw)
To: ltp
On 08/16/2018 02:16 PM, Petr Vorel wrote:
> Hi Alexey,
>
>>>> Hi Petr,
>
>>>> Since the server waits for requests from the client, the timeout
>>>> value for UDP/DCCP is the same as for the other protocols. Also the
>>>> server starts earlier than the client, so it should wait some time
>>>> to get the client requests.
>
>>>> I've changed the client side only because either request from the
>>>> client or reply from the server might be lost.
>
>>> Thanks for your explanation.
>>> I mean: UDP itself is the only protocol which don't support listen() so
>>> netstress server using UDP timeouts after some time. The default is 100ms.
>
>> Hmm, for the server the default should be 60 sec. Does it timeout earlier?
> Yes. The timeout is affected by value of -m. Thats' what I meant by my previous:
> $ date +"%T.%3N"; testcases/network/netstress/netstress -m 1 -T udp; date +"%T.%3N"
> 15:52:34.501
> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
> The timeout is actually 1ms. Try it with -m 1000 and it'll be indeed 1s
> netstress.c:917: INFO: max requests '3'
> netstress.c:944: INFO: using UDP
> netstress.c:676: INFO: assigning a name to the server socket...
> netstress.c:683: INFO: bind to port 47728
> netstress.c:575: FAIL: recv failed, sock '3'
> netstress.c:642: BROK: Server closed
> ...
> 15:52:34.516
>
>
> This is caused by udp/udp_lite not using listen(), but maybe is should be at
> least mentioned in help (if wanted behavior).
Agree.
Thanks,
Alexey
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2018-08-16 12:01 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-07-19 12:53 [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
2018-07-19 12:53 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
2018-07-23 6:22 ` Alexey Kodanev
2018-07-24 14:14 ` Petr Vorel
2018-07-27 10:24 ` Alexey Kodanev
2018-07-26 7:45 ` [LTP] [PATCH 1/2] netstress: TCONF on wrong -T parameter Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2018-08-09 15:23 [LTP] [PATCH RFC 1/4] lib/tst_test.c: add 'needs_drivers' option with tst_check_drivers cmd Alexey Kodanev
2018-08-09 15:23 ` [LTP] [PATCH RFC 4/4] network/ipsec: replace ipsec_try() with TST_RTNL_CHK() Alexey Kodanev
2018-08-16 11:16 ` [LTP] [RFC PATCH 2/2] netstress: Update help for -m behavior Petr Vorel
2018-08-16 12:01 ` Alexey Kodanev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox