summaryrefslogtreecommitdiff
path: root/include/linux/stackprotector.h
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-11-11 12:41:49 +0100
committerChristian Brauner <brauner@kernel.org>2026-11-11 12:41:49 +0100
commit2cca8a6f6ae690755862f5b633125119dcf6bd0c (patch)
tree58ce71caa459f2444802ba80226e2bad565b56de /include/linux/stackprotector.h
parent256fc12b1c95dae30109697efdc9d5bacf1a0aa5 (diff)
parent4c8b94e59b5f5bfdc0b36d080b6481c9d4ee3baf (diff)
Merge patch series "ns: fixes identifier fixes"
Christian Brauner <brauner@kernel.org> says: The namespace_init hooks see a namespace id of zero because the id is only allocated after the hook has run. The id is the only identifier of a namespace that is never recycled. So it's what a bpf LSM wants to use to track a namespace from namespace_init until namespace_free. The inode number is recycled way too quickly for that. So allocate the id in __ns_common_init() before the hook is called. Then ns_tree_add() doesn't need to allocate ids anymore and ns_tree_add_raw() can go. Landlock now logs that id instead of zero when it denies the creation of a namespace. * patches from https://patch.msgid.link/20261029-work-security-namespace_free-v2-0-65591dbba7b3@kernel.org: nstree: drop ns_tree_add_raw() ns: allocate the namespace id before the namespace_init hook bpf: don't mark namespace_init and namespace_free arguments as trusted Link: https://patch.msgid.link/20261029-work-security-namespace_free-v2-0-65591dbba7b3@kernel.org Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'include/linux/stackprotector.h')
0 files changed, 0 insertions, 0 deletions