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: <b45bdefe-ee3b-4a07-a397-0b2f87ca56d3@mojatatu.com>
Date: Sat, 3 Feb 2024 17:15:32 -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 03/02/2024 02:00, Jakub Kicinski wrote:
> On Thu,  1 Feb 2024 23:07:26 -0300 Victor Nogueira wrote:
>> Add 8 new mirred tdc tests that target mirred to block:
>>
>> - Add mirred mirror to egress block action
>> - Add mirred mirror to ingress block action
>> - Add mirred redirect to egress block action
>> - Add mirred redirect to ingress block action
>> - Try to add mirred action with both dev and block
>> - Try to add mirred action without specifying neither dev nor block
>> - Replace mirred redirect to dev action with redirect to block
>> - Replace mirred redirect to block action with mirror to dev
> 
> 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.
cheers,
Victor