arch/x86/um/vdso/vma.c

File Facts

System

Linux kernel

Corpus path

arch/x86/um/vdso/vma.c

Extension

.c

Size

1168 bytes

Lines

56

Domain

Architecture Layer

Bucket

arch/x86

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• 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/slab.h
• linux/sched.h
• linux/mm.h
• asm/page.h
• asm/elf.h
• linux/init.h

Detected Declarations

• function init_vdso
• function arch_setup_additional_pages
• module init init_vdso

Annotated Snippet

subsys_initcall(init_vdso);

int arch_setup_additional_pages(struct linux_binprm *bprm, int uses_interp)
{
	struct vm_area_struct *vma;
	struct mm_struct *mm = current->mm;
	static struct vm_special_mapping vdso_mapping = {
		.name = "[vdso]",
		.pages = &um_vdso,
	};

	if (mmap_write_lock_killable(mm))
		return -EINTR;

	vma = _install_special_mapping(mm, um_vdso_addr, PAGE_SIZE,
		VM_READ|VM_EXEC|
		VM_MAYREAD|VM_MAYWRITE|VM_MAYEXEC,
		&vdso_mapping);

	mmap_write_unlock(mm);

	return IS_ERR(vma) ? PTR_ERR(vma) : 0;
}

Annotation

• Immediate include surface: `linux/slab.h`, `linux/sched.h`, `linux/mm.h`, `asm/page.h`, `asm/elf.h`, `linux/init.h`.
• Detected declarations: `function init_vdso`, `function arch_setup_additional_pages`, `module init init_vdso`.
• Atlas domain: Architecture Layer / arch/x86.
• 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.