From: patchwork-bot+netdevbpf@kernel.org
To: Matteo Croce <technoboy85@gmail.com>
Cc: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
andrii@kernel.org, brauner@kernel.org, song@kernel.org,
linux-kernel@vger.kernel.org, teknoraver@meta.com
Subject: Re: [PATCH bpf-next] selftests/bpf: don't call fsopen() as privileged user
Date: Tue, 01 Jul 2025 21:00:07 +0000 [thread overview]
Message-ID: <175140360726.116693.10341336783596879643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701183123.31781-1-technoboy85@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 1 Jul 2025 20:31:23 +0200 you wrote:
> From: Matteo Croce <teknoraver@meta.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
next prev parent reply other threads:[~2025-07-01 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 18:31 [PATCH bpf-next] selftests/bpf: don't call fsopen() as privileged user Matteo Croce
2025-07-01 21:00 ` patchwork-bot+netdevbpf [this message]
2025-07-02 8:32 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175140360726.116693.10341336783596879643.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=song@kernel.org \
--cc=technoboy85@gmail.com \
--cc=teknoraver@meta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.