Re: [PATCH bpf-next 0/8] BPF LSM xattrs at inode creation support

[patchwork-bot+netdevbpf@kernel.org]

Hello:

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

On Tue, 15 Sep 2026 17:07:31 +0200 you wrote:
> Many in-kernel LSMs store security labels in extended file system attributes
> (xattrs). For these LSMs, atomic labeling during inode creation is critical:
> If the inode becomes accessible before its xattr is set, it is briefly
> unlabeled, which can disrupt LSMs making policy decisions based on file
> labels. Existing LSMs solve this by setting xattrs in the inode_init_security
> hook, which runs before the inode becomes accessible. BPF LSM programs
> currently lack this capability, and this series addresses this gap along
> with BPF selftests. Thanks!
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/8] ocfs2: Copy the xattr name in ocfs2_initxattrs
    (no matching commit)
  - [bpf-next,2/8] bpf, lsm: Reject writes into the BPF LSM program context
    https://git.kernel.org/bpf/bpf-next/c/c42da1d3ba9d
  - [bpf-next,3/8] bpf: Support passing context output arguments to kfuncs
    https://git.kernel.org/bpf/bpf-next/c/806fc431e0a3
  - [bpf-next,4/8] bpf, lsm: Let BPF LSM provide xattrs at inode creation
    https://git.kernel.org/bpf/bpf-next/c/ff0d1c0915d1
  - [bpf-next,5/8] bpf, lsm: Mark the BPF LSM hook overrides noinline
    https://git.kernel.org/bpf/bpf-next/c/3479e396eef4
  - [bpf-next,6/8] selftests/bpf: Test that the BPF LSM context is read-only
    https://git.kernel.org/bpf/bpf-next/c/e5d960cfe1d3
  - [bpf-next,7/8] selftests/bpf: Add verifier tests for the __ctx_out plumbing
    https://git.kernel.org/bpf/bpf-next/c/2757e9e53900
  - [bpf-next,8/8] selftests/bpf: Add tests for BPF LSM inode init labelling
    https://git.kernel.org/bpf/bpf-next/c/90dd01b6c1f3

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