From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, lennart@poettering.net
Subject: Re: [PATCH bpf-next 1/2] libbpf: ensure libbpf always opens files with O_CLOEXEC
Date: Fri, 26 May 2023 10:10:20 +0000 [thread overview]
Message-ID: <168509582014.13367.5683684106261979910.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230525221311.2136408-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 25 May 2023 15:13:10 -0700 you wrote:
> Make sure that libbpf code always gets FD with O_CLOEXEC flag set,
> regardless if file is open through open() or fopen(). For the latter
> this means to add "e" to mode string, which is supported since pretty
> ancient glibc v2.7.
>
> I also dropped outdated TODO comment in usdt.c, which was already completed.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: ensure libbpf always opens files with O_CLOEXEC
https://git.kernel.org/bpf/bpf-next/c/59842c5451fe
- [bpf-next,2/2] libbpf: ensure FD >= 3 during bpf_map__reuse_fd()
https://git.kernel.org/bpf/bpf-next/c/4aadd2920b81
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:[~2023-05-26 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 22:13 [PATCH bpf-next 1/2] libbpf: ensure libbpf always opens files with O_CLOEXEC Andrii Nakryiko
2023-05-25 22:13 ` [PATCH bpf-next 2/2] libbpf: ensure FD >= 3 during bpf_map__reuse_fd() Andrii Nakryiko
2023-05-26 8:19 ` [PATCH bpf-next 1/2] libbpf: ensure libbpf always opens files with O_CLOEXEC Lennart Poettering
2023-05-26 9:19 ` Daniel Borkmann
2023-05-26 10:10 ` 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=168509582014.13367.5683684106261979910.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=lennart@poettering.net \
--cc=martin.lau@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox