security/lsm_init.c

File Facts

System

Linux kernel

Corpus path

security/lsm_init.c

Extension

.c

Size

14986 bytes

Lines

569

Domain

Core OS

Bucket

Security And Isolation

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/lsm_hooks.h
• lsm.h

Detected Declarations

• function lsm_order_for_each
• function lsm_choose_security
• function lsm_choose_lsm
• function lsm_debug_enable
• function lsm_enabled_set
• function lsm_is_enabled
• function lsm_order_exists
• function lsm_order_for_each
• function lsm_order_append
• function lsm_order_parse
• function lsm_for_each_raw
• function lsm_for_each_raw
• function lsm_for_each_raw
• function lsm_blob_size_update
• function lsm_prepare
• function lsm_init_single
• function lsm_static_call_init
• function security_add_hooks
• function early_security_init
• function lsm_early_for_each_raw
• function security_init
• function security_initcall_pure
• function security_initcall_early
• function security_initcall_core
• function security_initcall_subsys
• function security_initcall_fs
• function security_initcall_device
• function security_initcall_late
• module init security_initcall_core
• module init security_initcall_subsys
• module init security_initcall_fs
• module init security_initcall_device

Annotated Snippet

core_initcall(security_initcall_core);

/**
 * security_initcall_subsys - Run the LSM subsys initcalls
 */
static int __init security_initcall_subsys(void)
{
	return lsm_initcall(subsys);
}
subsys_initcall(security_initcall_subsys);

/**
 * security_initcall_fs - Run the LSM fs initcalls
 */
static int __init security_initcall_fs(void)
{
	return lsm_initcall(fs);
}
fs_initcall(security_initcall_fs);

/**
 * security_initcall_device - Run the LSM device initcalls
 */
static int __init security_initcall_device(void)
{
	return lsm_initcall(device);
}
device_initcall(security_initcall_device);

/**
 * security_initcall_late - Run the LSM late initcalls
 */
static int __init security_initcall_late(void)
{
	int rc;

	rc = lsm_initcall(late);
	lsm_pr_dbg("all enabled LSMs fully activated\n");
	call_blocking_lsm_notifier(LSM_STARTED_ALL, NULL);

	return rc;
}
late_initcall(security_initcall_late);

Annotation

• Immediate include surface: `linux/init.h`, `linux/lsm_hooks.h`, `lsm.h`.
• Detected declarations: `function lsm_order_for_each`, `function lsm_choose_security`, `function lsm_choose_lsm`, `function lsm_debug_enable`, `function lsm_enabled_set`, `function lsm_is_enabled`, `function lsm_order_exists`, `function lsm_order_for_each`, `function lsm_order_append`, `function lsm_order_parse`.
• Atlas domain: Core OS / Security And Isolation.
• Implementation status: integration implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.