netdev - Re: [PATCH net-next] selftests: tc-testing: add mirred to block tdc tests

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: <4342ac71-105f-4ed4-83b7-ede3ab7255f2@mojatatu.com>
Date: Mon, 5 Feb 2024 13:28:22 -0300
From: Victor Nogueira <victor@...atatu.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, davem@...emloft.net,
 edumazet@...gle.com, pabeni@...hat.com, netdev@...r.kernel.org,
 kernel@...atatu.com, pctammela@...atatu.com
Subject: Re: [PATCH net-next] selftests: tc-testing: add mirred to block tdc
 tests

On 04/02/2024 13:33, Jakub Kicinski wrote:
> On Sat, 3 Feb 2024 17:15:32 -0300 Victor Nogueira wrote:
>>> I think this breaks the TDC runner.
>>> I'll toss it from patchwork, I can revive it when TDC is fixed (or you
>>> tell me that I'm wrong).
>>
>> Oh, I think you caught an issue with the process.
>> The executor was using the release iproute2 instead of iproute2-next,
>> which I tested on. I'm wondering if other tests in nipa are using
>> iproute2-next or release iproute2. The issue only arises if you have
>> patches in net-next that are not in the release iproute2. We will fix
>> the executor shortly.
> 
> We merge iproute2 into iprout2-next locally and build the combined
> thing, FWIW. I haven't solved the problem of pending patches, yet,
> tho :( If the iproute2-next patches are just on the list but not
> merged the new tests will fail.

In this case both were merged into -next trees. It's just the executor
that needed fixing.
For features merged into net-next but not yet in iproute2-next perhaps
nipa can be used to catch such issues?
Should I resend the patch now that the executor is fixed?