Re: [PATCH bpf-next 1/2] libbpf: ensure libbpf always opens files with O_CLOEXEC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

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

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






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux