netdev - Re: Any hardware limitation for bpf testing?

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

Date:   Wed, 01 Nov 2017 21:39:38 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Orson Zhai <orson.zhai@...aro.org>
CC:     netdev@...r.kernel.org, Sumit Semwal <sumit.semwal@...aro.org>
Subject: Re: Any hardware limitation for bpf testing?

On 11/01/2017 12:16 PM, Orson Zhai wrote:
[...]
> We have ran some bpf test within kselftest for 4.14.0-rc5-next-20171018 at
> some hardware resource limited devices. Say Hikey Board (arm64 core) with
> 2GB memory.
>
> The test processes was killed by OOM which made the test failed.
>
> We investigate the reason and find bpf test will require a large mount of
> memory to run.
>
> Like some code in selftests/bpf/test_maps.c
>
>> static void test_hashmap_walk(int task, void *data)
>> {
>>       int fd, i, max_entries = 100000;
>                                           ^^^^^^^^^^^^
>>        ......
>>       }
>
> The test will pass smoothly when we set max_entries to a smaller number.

Feel free to send a patch to set this to something lower, maybe 10k
or such, if that will work for your setup.

Thanks,
Daniel