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] [day] [month] [year] [list]

Message-ID: <20250702-liberal-leerung-f2a973398c3e@brauner>
Date: Wed, 2 Jul 2025 10:32:47 +0200
From: Christian Brauner <brauner@...nel.org>
To: Matteo Croce <technoboy85@...il.com>
Cc: bpf@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	Andrii Nakryiko <andrii@...nel.org>, Song Liu <song@...nel.org>, linux-kernel@...r.kernel.org, 
	Matteo Croce <teknoraver@...a.com>
Subject: Re: [PATCH bpf-next] selftests/bpf: don't call fsopen() as
 privileged user

On Tue, Jul 01, 2025 at 08:31:23PM +0200, Matteo Croce 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.
> 
> cfr. https://github.com/systemd/systemd/pull/36134
> 
> Signed-off-by: Matteo Croce <teknoraver@...a.com>
> ---

Thanks!
Acked-by: Christian Brauner <brauner@...nel.org>