[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165653881365.30550.15940066910957186806.git-patchwork-notify@kernel.org>
Date: Wed, 29 Jun 2022 21:40:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Quentin Monnet <quentin@...valent.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, bpf@...r.kernel.org,
netdev@...r.kernel.org, sdf@...gle.com, laoar.shao@...il.com
Subject: Re: [PATCH bpf-next v2] bpftool: Probe for memcg-based accounting before
bumping rlimit
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Wed, 29 Jun 2022 12:13:51 +0100 you wrote:
> Bpftool used to bump the memlock rlimit to make sure to be able to load
> BPF objects. After the kernel has switched to memcg-based memory
> accounting [0] in 5.11, bpftool has relied on libbpf to probe the system
> for memcg-based accounting support and for raising the rlimit if
> necessary [1]. But this was later reverted, because the probe would
> sometimes fail, resulting in bpftool not being able to load all required
> objects [2].
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpftool: Probe for memcg-based accounting before bumping rlimit
https://git.kernel.org/bpf/bpf-next/c/f0cf642c56b7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists