lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Oct 2021 19:17:47 -0600
From:   David Ahern <>
To:     Leonard Crestez <>,
        Jakub Kicinski <>,
        Shuah Khan <>, David Ahern <>
Cc:     "David S. Miller" <>,
        Ido Schimmel <>,
        Seth David Schoen <>,,,
Subject: Re: [PATCH 11/11] selftests: net/fcnal: Reduce client timeout

On 10/6/21 3:26 PM, Leonard Crestez wrote:
> On 06.10.2021 18:01, David Ahern wrote:
>> On 10/6/21 5:47 AM, Leonard Crestez wrote:
>>> Reduce default client timeout from 5 seconds to 500 miliseconds.
>>> Can be overridden from environment by exporting NETTEST_CLIENT_TIMEOUT=5
>>> Some tests need ICMP timeouts so pass an explicit -t5 for those.
>>> Signed-off-by: Leonard Crestez <>
>>> ---
>>>   tools/testing/selftests/net/ | 17 +++++++++++------
>>>   1 file changed, 11 insertions(+), 6 deletions(-)
>> The problem with blindly reducing the timeouts is running the script on
>> a loaded server. Some tests are expected to timeout while for tests a
>> timeout is a failure.
> Keeping the default value "5" would be fine as long as it is possible to
> override externally and get fast results on a mostly-idle machine.

5 is the default for nettest.c; the test script passes in -t1 for all tests.

> Placing a default value in the environment which is overriden by certain
> tests achieves that.
> In theory it would also be possible for to parse as
> "--timeout" option and pass it into every single test but that solution
> would cause much more code churn.
> Having default values in environment variables that can still be
> overridden by command-line arguments is a common pattern in many tools.
> It also avoids having to pass-through every flag through every
> intermediate wrapper.

I do not agree with env variables here.

Powered by blists - more mailing lists