netdev - Re: [PATCH bpf-next 0/2] bpftool: Restore memlock rlimit bump

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: <165523903505.29335.14557399406891586610.git-patchwork-notify@kernel.org>
Date:   Tue, 14 Jun 2022 20:37:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Quentin Monnet <quentin@...valent.com>
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        laoar.shao@...il.com, harshmodi@...gle.com, paul@...ium.io,
        netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpftool: Restore memlock rlimit bump

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Fri, 10 Jun 2022 12:26:46 +0100 you wrote:
> We recently removed the uncondtional rlimit bump from bpftool, deferring it
> to libbpf to probe the system for memcg-based memory accounting and to
> raise the rlimit if necessary.
> 
> This probing is based on the availability of a given BPF helper, and his
> known to fail on some environments where the helper, but not the memcg
> memory accounting, has been backported.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] Revert "bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK"
    https://git.kernel.org/bpf/bpf-next/c/6b4384ff1088
  - [bpf-next,2/2] bpftool: Do not check return value from libbpf_set_strict_mode()
    https://git.kernel.org/bpf/bpf-next/c/93270357daa9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html