netdev - Re: [PATCH net-next] selftests: net: fib_nexthops: Wait before checking reported idle time

lists.openwall.net		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] [day] [month] [year] [list]

Message-Id: <163274160669.1534.16948830320310763673.git-patchwork-notify@kernel.org>
Date:   Mon, 27 Sep 2021 11:20:06 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Petr Machata <petrm@...dia.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org
Subject: Re: [PATCH net-next] selftests: net: fib_nexthops: Wait before checking
 reported idle time

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri, 24 Sep 2021 12:04:27 +0200 you wrote:
> The purpose of this test is to verify that after a short activity passes,
> the reported time is reasonable: not zero (which could be reported by
> mistake), and not something outrageous (which would be indicative of an
> issue in used units).
> 
> However, the idle time is reported in units of clock_t, or hundredths of
> second. If the initial sequence of commands is very quick, it is possible
> that the idle time is reported as just flat-out zero. When this test was
> recently enabled in our nightly regression, we started seeing spurious
> failures for exactly this reason.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: net: fib_nexthops: Wait before checking reported idle time
    https://git.kernel.org/netdev/net-next/c/b69c99463d41

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html