netdev - Re: [TEST] gre_multipath_nh

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: <ZdOG8oxNu5gOImDd@shredder>
Date: Mon, 19 Feb 2024 18:50:58 +0200
From: Ido Schimmel <idosch@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Petr Machata <petrm@...dia.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [TEST] gre_multipath_nh_res takes forever

Hi,

On Thu, Feb 15, 2024 at 09:50:05AM -0800, Jakub Kicinski wrote:
> Hi!
> 
> I bumped the timeouts for forwarding tests with kernel debug enabled
> yesterday, and gre_multipath_nh_res still doesn't finish even tho it
> runs for close to 3 hours. On a non-debug kernel it takes around 30min.
> 
> You probably have a better idea how to address this than me, but it
> seems to time out on the IPv6 tests - I wonder if using mausezahn 
> instead of ping for IPv6 would help a bit?

Converted from ping6 to mausezahn, but the test was still relatively
slow because of the 1msec delay we pass the mausezahn. After converting
to mausezahn and removing the delay the runtime dropped from ~350
seconds to ~15 seconds on my system.

I think I will parametrize the delay for platforms that might need it,
but default it to 0 as it's not needed with veth. The same change is
needed in other tests. Will submit it together with Petr's selftest
changes.