netdev - Re: [PATCH net-next] selftests/net: force synchronized GC for a test.

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: <8a5c0919075a964ae8ada94e5ee9e104917cbf67.camel@redhat.com>
Date: Tue, 27 Feb 2024 09:53:42 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Kui-Feng Lee <sinquersw@...il.com>, Jakub Kicinski <kuba@...nel.org>, 
	Kui-Feng Lee <thinker.li@...il.com>
Cc: netdev@...r.kernel.org, ast@...nel.org, martin.lau@...ux.dev, 
 kernel-team@...a.com, davem@...emloft.net, dsahern@...nel.org,
 kuifeng@...a.com
Subject: Re: [PATCH net-next] selftests/net: force synchronized GC for a
 test.

On Fri, 2024-02-23 at 20:40 -0800, Kui-Feng Lee wrote:
> 
> On 2/23/24 18:21, Jakub Kicinski wrote:
> > On Fri, 23 Feb 2024 00:13:46 -0800 Kui-Feng Lee wrote:
> > > Due to the slowness of the test environment
> > 
> > Would be interesting if it's slowness, because it failed 2 times
> > on the debug runner but 5 times on the non-debug one. We'll see.
> 
> The code was landed on Feb 12, 2024.
> It is actually 1 time with debug runner but 3 times on the non-debug 
> one. 1 time with debug runner and 2 times with the non-debug runner 
> happened in a 12 hours period.

The only failure in a debug run was causes by an unrelated issue:

https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/467362/7-fib-tests-sh/stdout

(grep for UBSAN)

Basically the problems happens quite sporadically only in "fast" env. I
think it's worthy a deeper investigation (it sounds like a race
somewhere).

I guess/hope then raising the number of temporary and permanent routes
created by the relevant test-case could help making the issue more
easily reproducible.

Thanks,

Paolo