init/do_mounts.h

File Facts

System

Linux kernel

Corpus path

init/do_mounts.h

Extension

.h

Size

1043 bytes

Lines

43

Domain

Core OS

Bucket

Boot And Init

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/kernel.h
• linux/blkdev.h
• linux/init.h
• linux/syscalls.h
• linux/unistd.h
• linux/slab.h
• linux/mount.h
• linux/major.h
• linux/root_dev.h
• linux/init_syscalls.h
• linux/task_work.h
• linux/file.h

Detected Declarations

• function create_dev
• function rd_load_image
• function initrd_load

Annotated Snippet

static inline int rd_load_image(void) { return 0; }
#endif

#ifdef CONFIG_BLK_DEV_INITRD
void __init initrd_load(void);
#else
static inline void initrd_load(void) { }
#endif

/* Ensure that async file closing finished to prevent spurious errors. */
static inline void init_flush_fput(void)
{
	flush_delayed_fput();
	task_work_run();
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/blkdev.h`, `linux/init.h`, `linux/syscalls.h`, `linux/unistd.h`, `linux/slab.h`, `linux/mount.h`, `linux/major.h`.
• Detected declarations: `function create_dev`, `function rd_load_image`, `function initrd_load`.
• Atlas domain: Core OS / Boot And Init.
• 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.