Re: [RFC PATCH 1/2] security: Add hook for unresolved pathname opens
From: bot+bpf-ci
Date: Fri Nov 20 2026 - 05:44:53 EST
> security: Add hook for unresolved pathname opens
TL;DR: Commit message only: it lists what the new file_open_name LSM hook
changes but not why it is needed, what existing hooks can't enforce, or which
LSM will use it.
> security: Add hook for unresolved pathname opens
>
> Check the copied pathname against the selected base before traversal or
> file changes, including O_PATH and O_TMPFILE.
> Pass lookup flags so policy can request a referenced retry. Recheck the
> base after each restart and cover kernel opens with an explicit root.
>
> Signed-off-by: Anastasios Papagiannis <tasos.papagiannnis@xxxxxxxxx>
This isn't a bug, but could the changelog say why a pre-lookup pathname hook
is needed, meaning what security_file_open(), security_inode_permission() and
the path hooks cannot enforce, and which LSM is expected to use it?
Each sentence currently lists what the patch changes (the call in
path_init(), the lookup_flags argument, the recheck on each path_openat()
retry, the ND_ROOT_PRESET case), but the problem being solved is not stated.
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/44717653250