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: <YvJuuTnEaSng3y4Y@shredder>
Date:   Tue, 9 Aug 2022 17:27:05 +0300
From:   Ido Schimmel <idosch@...dia.com>
To:     Jiri Pirko <jiri@...dia.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        pabeni@...hat.com, edumazet@...gle.com, amcohen@...dia.com,
        dsahern@...il.com, ivecera@...hat.com, mlxsw@...dia.com
Subject: Re: [PATCH net] selftests: forwarding: Fix failing tests with old
 libnet

On Tue, Aug 09, 2022 at 03:10:02PM +0200, Jiri Pirko wrote:
> Not directly related to this, but I was wondering, if it would be
> possible to use $IP and allow user to replace the system-wide "ip" for
> testing purposes...

When testing iproute2 patches (mine or from the ML) I usually do:

export PATH=/home/idosch/code/iproute2/ip/:/home/idosch/code/iproute2/devlink/:/home/idosch/code/iproute2/bridge:$PATH

As part of regression we just compile and install iproute2 from git

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ