netdev - Re: [PATCH bpf-next v4] libbpf: fix probe code to return EPERM if encountered

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]

Message-ID: <1c706733-47cb-0216-e8a6-214979af7494@iogearbox.net>
Date:   Wed, 13 May 2020 16:57:08 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Eelco Chaudron <echaudro@...hat.com>, bpf@...r.kernel.org
Cc:     davem@...emloft.net, netdev@...r.kernel.org, ast@...nel.org,
        kafai@...com, songliubraving@...com, yhs@...com, andriin@...com,
        toke@...hat.com
Subject: Re: [PATCH bpf-next v4] libbpf: fix probe code to return EPERM if
 encountered

On 5/12/20 11:04 AM, Eelco Chaudron wrote:
> When the probe code was failing for any reason ENOTSUP was returned, even
> if this was due to no having enough lock space. This patch fixes this by
> returning EPERM to the user application, so it can respond and increase
> the RLIMIT_MEMLOCK size.
> 
> Signed-off-by: Eelco Chaudron <echaudro@...hat.com>

Applied, thanks!