linux-kernel - Re: [PATCH bpf-next] selftests/bpf: don't call fsopen() as privileged user

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: 
 <175140360726.116693.10341336783596879643.git-patchwork-notify@kernel.org>
Date: Tue, 01 Jul 2025 21:00:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Matteo Croce <technoboy85@...il.com>
Cc: bpf@...r.kernel.org, linux-fsdevel@...r.kernel.org, andrii@...nel.org,
 brauner@...nel.org, song@...nel.org, linux-kernel@...r.kernel.org,
 teknoraver@...a.com
Subject: Re: [PATCH bpf-next] selftests/bpf: don't call fsopen() as privileged
 user

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:

On Tue,  1 Jul 2025 20:31:23 +0200 you wrote:
> From: Matteo Croce <teknoraver@...a.com>
> 
> In the BPF token example, the fsopen() syscall is called as privileged
> user. This is unneeded because fsopen() can be called also as
> unprivileged user from the user namespace.
> As the `fs_fd` file descriptor which was sent back and fort is still the
> same, keep it open instead of cloning and closing it twice via SCM_RIGHTS.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: don't call fsopen() as privileged user
    https://git.kernel.org/bpf/bpf-next/c/212ec9229567

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html