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] [day] [month] [year] [list]
Date:   Thu, 8 Feb 2018 00:34:57 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        linux-kselftest@...r.kernel.org, netdev@...r.kernel.org
Cc:     shuahkh@....samsung.com, shuah@...nel.org,
        alexei.starovoitov@...il.com, ast@...nel.org
Subject: Re: [PATCH v2] selftests: bpf: test_kmod.sh: check the module path
 before insmod

On 02/07/2018 07:15 PM, Naresh Kamboju wrote:
> test_kmod.sh reported false failure when module not present.
> Check test_bpf.ko is present in the path before loading it.
> 
> Two cases to be addressed here,
> In the development process of test_bpf.c unit testing will be done by
> developers by using "insmod $SRC_TREE/lib/test_bpf.ko"
> 
> On the other hand testers run full tests by installing modules on device
> under test (DUT) and followed by modprobe to insert the modules accordingly.
> 
> Signed-off-by: Naresh Kamboju <naresh.kamboju@...aro.org>

Applied to bpf tree, thanks Naresh!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ