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:   Sat, 4 May 2019 23:24:40 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Yonghong Song <yhs@...com>
Cc:     bpf <bpf@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next] selftests/bpf: set RLIMIT_MEMLOCK properly for test_libbpf_open.c

On Mon, Apr 29, 2019 at 5:01 PM Yonghong Song <yhs@...com> wrote:
>
> Test test_libbpf.sh failed on my development server with failure
>   -bash-4.4$ sudo ./test_libbpf.sh
>   [0] libbpf: Error in bpf_object__probe_name():Operation not permitted(1).
>       Couldn't load basic 'r0 = 0' BPF program.
>   test_libbpf: failed at file test_l4lb.o
>   selftests: test_libbpf [FAILED]
>   -bash-4.4$
>
> The reason is because my machine has 64KB locked memory by default which
> is not enough for this program to get locked memory.
> Similar to other bpf selftests, let us increase RLIMIT_MEMLOCK
> to infinity, which fixed the issue.
>
> Signed-off-by: Yonghong Song <yhs@...com>

Applied. Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ