[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200623.203658.1101064165283196227.davem@davemloft.net>
Date: Tue, 23 Jun 2020 20:36:58 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: tannerlove.kernel@...il.com
Cc: netdev@...r.kernel.org, tannerlove@...gle.com, willemb@...gle.com
Subject: Re: [PATCH net-next] selftests/net: plug rxtimestamp test into
kselftest framework
From: Tanner Love <tannerlove.kernel@...il.com>
Date: Mon, 22 Jun 2020 13:43:24 -0400
> From: tannerlove <tannerlove@...gle.com>
>
> Run rxtimestamp as part of TEST_PROGS. Analogous to other tests, add
> new rxtimestamp.sh wrapper script, so that the test runs isolated
> from background traffic in a private network namespace.
>
> Also ignore failures of test case #6 by default. This case verifies
> that a receive timestamp is not reported if timestamp reporting is
> enabled for a socket, but generation is disabled. Receive timestamp
> generation has to be enabled globally, as no associated socket is
> known yet. A background process that enables rx timestamp generation
> therefore causes a false positive. Ntpd is one example that does.
>
> Add a "--strict" option to cause failure in the event that any test
> case fails, including test #6. This is useful for environments that
> are known to not have such background processes.
>
> Tested:
> make -C tools/testing/selftests TARGETS="net" run_tests
>
> Signed-off-by: Tanner Love <tannerlove@...gle.com>
> Acked-by: Willem de Bruijn <willemb@...gle.com>
Applied, thanks.
Powered by blists - more mailing lists