kernel/exec_domain.c

File Facts

System

Linux kernel

Corpus path

kernel/exec_domain.c

Extension

.c

Size

1094 bytes

Lines

47

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: syscall or user/kernel boundary

Status

core 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.
• Defines or participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/kernel.h
• linux/kmod.h
• linux/module.h
• linux/personality.h
• linux/proc_fs.h
• linux/sched.h
• linux/seq_file.h
• linux/syscalls.h
• linux/sysctl.h
• linux/types.h

Detected Declarations

• syscall personality
• function ABIs
• function proc_execdomains_init
• module init proc_execdomains_init

Annotated Snippet

SYSCALL_DEFINE1(personality, unsigned int, personality)
{
	unsigned int old = current->personality;

	if (personality != 0xffffffff)
		set_personality(personality);

	return old;
}

Annotation

• Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/kmod.h`, `linux/module.h`, `linux/personality.h`, `linux/proc_fs.h`, `linux/sched.h`, `linux/seq_file.h`.
• Detected declarations: `syscall personality`, `function ABIs`, `function proc_execdomains_init`, `module init proc_execdomains_init`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• Implementation status: core 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.