From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <quentin@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
laoar.shao@gmail.com, harshmodi@google.com, paul@cilium.io,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpftool: Restore memlock rlimit bump
Date: Tue, 14 Jun 2022 20:37:15 +0000 [thread overview]
Message-ID: <165523903505.29335.14557399406891586610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220610112648.29695-1-quentin@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.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
prev parent reply other threads:[~2022-06-14 20:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:26 [PATCH bpf-next 0/2] bpftool: Restore memlock rlimit bump Quentin Monnet
2022-06-10 11:26 ` [PATCH bpf-next 1/2] Revert "bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK" Quentin Monnet
2022-06-10 16:07 ` sdf
2022-06-10 16:34 ` Quentin Monnet
2022-06-10 16:46 ` Stanislav Fomichev
2022-06-10 17:00 ` Quentin Monnet
2022-06-10 17:17 ` Stanislav Fomichev
2022-06-14 12:37 ` Yafang Shao
2022-06-14 14:20 ` Quentin Monnet
2022-06-14 20:34 ` Daniel Borkmann
2022-06-14 21:01 ` Stanislav Fomichev
2022-06-15 13:22 ` Yafang Shao
2022-06-15 15:52 ` Stanislav Fomichev
2022-06-15 16:05 ` Yafang Shao
2022-06-16 13:59 ` Quentin Monnet
2022-06-16 14:54 ` Yafang Shao
2022-06-16 18:07 ` Stanislav Fomichev
2022-06-16 20:40 ` Andrii Nakryiko
2022-06-10 11:26 ` [PATCH bpf-next 2/2] bpftool: Do not check return value from libbpf_set_strict_mode() Quentin Monnet
2022-06-14 20:37 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165523903505.29335.14557399406891586610.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=harshmodi@google.com \
--cc=laoar.shao@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul@cilium.io \
--cc=quentin@isovalent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.