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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221018110031.299ecb23@kernel.org>
Date:   Tue, 18 Oct 2022 11:00:31 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     wangyufen <wangyufen@...wei.com>
Cc:     Martin KaFai Lau <martin.lau@...ux.dev>,
        Lina Wang <lina.wang@...iatek.com>, <bpf@...r.kernel.org>,
        <davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
        <deso@...teo.net>, <netdev@...r.kernel.org>
Subject: Re: [net 1/2] selftests/net: fix opening object file failed

On Tue, 18 Oct 2022 17:50:19 +0800 wangyufen wrote:
> So, there are two possible approaches:  the first moving nat6to4.c and 
> the actual test programs to selftests/bpf;
> 
> second add make dependency on libbpf for the nat6to4.c.
> 
> Which one is better?

Can we move the programs and create a dependency from them back 
to networking? Perhaps shared components like udpgso_* need to live
under tools/net so they can be easily "depended on"?

Either that or they need to switch to a different traffic generator for
the BPF test, cause there's more networking selftests using the UDP
generators :(

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ