Re: [PATCH bpf-next] libbpf: call dup2() syscall directly - patchwork-bot+netdevbpf

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, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] libbpf: call dup2() syscall directly
Date: Tue, 23 Jan 2024 23:40:50 +0000	[thread overview]
Message-ID: <170605325018.25186.12613038676566222239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240119210201.1295511-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

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