netdev - Re: [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path

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] [day] [month] [year] [list]

Date:   Mon, 30 Jul 2018 09:48:25 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     petrm@...lanox.com
Cc:     netdev@...r.kernel.org, linux-kselftest@...r.kernel.org,
        shuah@...nel.org
Subject: Re: [PATCH net-next 0/5] A test for mirror-to-gretap with team in
 UL packet path

From: Petr Machata <petrm@...lanox.com>
Date: Mon, 30 Jul 2018 16:37:17 +0200

> This patchset adds a test for "tc action mirred mirror" where the
> mirrored-to device is a gretap, and underlay path contains a team
> device.
> 
> In patch #1 require_command() is added, which should henceforth be used
> to declare dependence on a certain tool.
> 
> In patch #2, two new functions, team_create() and team_destroy(), are
> added to lib.sh.
> 
> The newly-added test uses arping, which isn't necessarily available.
> Therefore patch #3 introduces $ARPING, and a preexisting test is fixed
> to require_command $ARPING.
> 
> In patches #4 and #5, two new tests are added. In both cases, a team
> device is on egress path of a mirrored packet in a mirror-to-gretap
> scenario. In the first one, the team device is in loadbalance mode, in
> the second one it's in lacp mode. (The difference in modes necessitates
> a different testing strategy, hence two test cases instead of just
> parameterizing one.)

I always like seeing new test cases. :)

Series applied, thanks.