netdev - Re: [PATCH net-next v3] selftests/net: fix waiting time for ipv6_gc test in fib

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: 
 <170987403755.8362.4504288196738104380.git-patchwork-notify@kernel.org>
Date: Fri, 08 Mar 2024 05:00:37 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kui-Feng Lee <thinker.li@...il.com>
Cc: netdev@...r.kernel.org, ast@...nel.org, martin.lau@...ux.dev,
 kernel-team@...a.com, kuba@...nel.org, davem@...emloft.net,
 dsahern@...nel.org, pabeni@...hat.com, sinquersw@...il.com, kuifeng@...a.com
Subject: Re: [PATCH net-next v3] selftests/net: fix waiting time for ipv6_gc test
 in fib_tests.sh.

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Tue,  5 Mar 2024 10:39:49 -0800 you wrote:
> ipv6_gc fails occasionally. According to the study, fib6_run_gc() using
> jiffies_round() to round the GC interval could increase the waiting time up
> to 750ms (3/4 seconds). The timer has a granularity of 512ms at the range
> 4s to 32s. That means a route with an expiration time E seconds can wait
> for more than E * 2 + 1 seconds if the GC interval is also E seconds.
> 
> E * 2 + 2 seconds should be enough for waiting for removing routes.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] selftests/net: fix waiting time for ipv6_gc test in fib_tests.sh.
    https://git.kernel.org/netdev/net-next/c/4af9a0bee116

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