security/selinux/initcalls.c
Source file repositories/reference/linux-study-clean/security/selinux/initcalls.c
File Facts
- System
- Linux kernel
- Corpus path
security/selinux/initcalls.c- Extension
.c- Size
- 859 bytes
- Lines
- 53
- Domain
- Core OS
- Bucket
- Security And Isolation
- Inferred role
- Core OS: implementation source
- Status
- source 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.
Dependency Surface
linux/init.hinitcalls.h
Detected Declarations
function selinux_initcall
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* SELinux initcalls
*/
#include <linux/init.h>
#include "initcalls.h"
/**
* selinux_initcall - Perform the SELinux initcalls
*
* Used as a device initcall in the SELinux LSM definition.
*/
int __init selinux_initcall(void)
{
int rc = 0, rc_tmp = 0;
rc_tmp = init_sel_fs();
if (!rc && rc_tmp)
rc = rc_tmp;
rc_tmp = sel_netport_init();
if (!rc && rc_tmp)
rc = rc_tmp;
rc_tmp = sel_netnode_init();
if (!rc && rc_tmp)
rc = rc_tmp;
rc_tmp = sel_netif_init();
if (!rc && rc_tmp)
rc = rc_tmp;
rc_tmp = sel_netlink_init();
if (!rc && rc_tmp)
rc = rc_tmp;
#if defined(CONFIG_SECURITY_INFINIBAND)
rc_tmp = sel_ib_pkey_init();
if (!rc && rc_tmp)
rc = rc_tmp;
#endif
#if defined(CONFIG_NETFILTER)
rc_tmp = selinux_nf_ip_init();
if (!rc && rc_tmp)
rc = rc_tmp;
#endif
return rc;
}
Annotation
- Immediate include surface: `linux/init.h`, `initcalls.h`.
- Detected declarations: `function selinux_initcall`.
- Atlas domain: Core OS / Security And Isolation.
- Implementation status: source 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.