[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220610112648.29695-1-quentin@isovalent.com>
Date: Fri, 10 Jun 2022 12:26:46 +0100
From: Quentin Monnet <quentin@...valent.com>
To: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>
Cc: Yafang Shao <laoar.shao@...il.com>,
Harsh Modi <harshmodi@...gle.com>,
Paul Chaignon <paul@...ium.io>, netdev@...r.kernel.org,
bpf@...r.kernel.org, Quentin Monnet <quentin@...valent.com>
Subject: [PATCH bpf-next 0/2] bpftool: Restore memlock rlimit bump
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.
To work around this, this set restores the memlock rlimit bump in bpftool.
Please see the description of the first patch for more details.
Quentin Monnet (2):
Revert "bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK"
bpftool: Do not check return value from libbpf_set_strict_mode()
tools/bpf/bpftool/common.c | 8 ++++++++
tools/bpf/bpftool/feature.c | 2 ++
tools/bpf/bpftool/main.c | 2 --
tools/bpf/bpftool/main.h | 2 ++
tools/bpf/bpftool/map.c | 2 ++
tools/bpf/bpftool/pids.c | 1 +
tools/bpf/bpftool/prog.c | 3 +++
tools/bpf/bpftool/struct_ops.c | 2 ++
8 files changed, 20 insertions(+), 2 deletions(-)
--
2.34.1
Powered by blists - more mailing lists