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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250416065223.4e4c4379@kernel.org>
Date: Wed, 16 Apr 2025 06:52:23 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: chia-yu.chang@...ia-bell-labs.com
Cc: xandfury@...il.com, netdev@...r.kernel.org, dave.taht@...il.com,
 pabeni@...hat.com, jhs@...atatu.com, stephen@...workplumber.org,
 xiyou.wangcong@...il.com, jiri@...nulli.us, davem@...emloft.net,
 edumazet@...gle.com, horms@...nel.org, andrew+netdev@...n.ch,
 donald.hunter@...il.com, ast@...erby.net, liuhangbin@...il.com,
 shuah@...nel.org, linux-kselftest@...r.kernel.org, ij@...nel.org,
 ncardwell@...gle.com, koen.de_schepper@...ia-bell-labs.com,
 g.white@...lelabs.com, ingemar.s.johansson@...csson.com,
 mirja.kuehlewind@...csson.com, cheshire@...le.com, rs.ietf@....at,
 Jason_Livingood@...cast.com, vidhi_goel@...le.com
Subject: Re: [PATCH v11 net-next 2/5] selftests/tc-testing: Add selftests
 for qdisc DualPI2

On Tue, 15 Apr 2025 14:43:14 +0200 chia-yu.chang@...ia-bell-labs.com
wrote:
> From: Chia-Yu Chang <chia-yu.chang@...ia-bell-labs.com>
> 
> Update configuration of tc-tests and preload DualPI2 module for self-tests,
> and add folloiwng self-test cases for DualPI2:
> 
>   Test a4c7: Create DualPI2 with default setting
>   Test 2130: Create DualPI2 with typical_rtt and max_rtt
>   Test 90c1: Create DualPI2 with max_rtt
>   Test 7b3c: Create DualPI2 with any_ect option
>   Test 49a3: Create DualPI2 with overflow option
>   Test d0a1: Create DualPI2 with drop_enqueue option
>   Test f051: Create DualPI2 with no_split_gso option

it appears applying this causes the tdc test runner to break,
could you take a look?

https://github.com/p4tc-dev/tc-executor/blob/storage/artifacts/79725/1-tdc-sh/stdout

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ