From: patchwork-bot+netdevbpf@kernel.org
To: Sergei Nizovtsev <snizovtsev@cloudlinux.com>
Cc: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
stable@vger.kernel.org, kpsingh@kernel.org, matt@bobrowski.net,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev, serge@hallyn.com,
amir73il@gmail.com, paul@paul-moore.com, brauner@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] bpf, lsm: Mark backing_file_alloc/free LSM hooks as untrusted
Date: Sat, 14 Nov 2026 06:10:05 +0000 [thread overview]
Message-ID: <179463660529.2025154.16083428356016903156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111203614.1221188-1-snizovtsev@cloudlinux.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 11 Nov 2026 21:35:52 +0100 you wrote:
> The backing_file_alloc and backing_file_free LSM hooks get the backing
> file as "struct file *backing_file", but its f_path is not populated
> while they run:
>
> - security_backing_file_alloc() is called from init_backing_file() in
> alloc_empty_backing_file(), before vfs_open() sets f_path, so
> backing_file->f_path.dentry is NULL;
> - security_backing_file_free() can run for a backing file whose open
> failed and whose f_path was already cleared.
>
> [...]
Here is the summary with links:
- [bpf] bpf, lsm: Mark backing_file_alloc/free LSM hooks as untrusted
https://git.kernel.org/bpf/bpf/c/ab86b62012b9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-14 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:35 [PATCH bpf] bpf, lsm: Mark backing_file_alloc/free LSM hooks as untrusted Sergei Nizovtsev
2026-11-11 21:02 ` sashiko-bot
2026-11-14 6:10 ` patchwork-bot+netdevbpf [this message]
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=179463660529.2025154.16083428356016903156.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amir73il@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=matt@bobrowski.net \
--cc=memxor@gmail.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=snizovtsev@cloudlinux.com \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox