Hello: This patch was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <ast@xxxxxxxxxx>: On Fri, 19 Jan 2024 13:02:01 -0800 you wrote: > We've ran into issues with using dup2() API in production setting, where > libbpf is linked into large production environment and ends up calling > uninteded custom implementations of dup2(). These custom implementations > don't provide atomic FD replacement guarantees of dup2() syscall, > leading to subtle and hard to debug issues. > > To prevent this in the future and guarantee that no libc implementation > will do their own custom non-atomic dup2() implementation, call dup2() > syscall directly with syscall(SYS_dup2). > > [...] Here is the summary with links: - [bpf-next] libbpf: call dup2() syscall directly https://git.kernel.org/bpf/bpf-next/c/bc308d011ab8 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html