fs/binfmt_script.c

File Facts

System

Linux kernel

Corpus path

fs/binfmt_script.c

Extension

.c

Size

4358 bytes

Lines

160

Domain

Core OS

Bucket

VFS And Filesystem Core

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/module.h
• linux/string.h
• linux/stat.h
• linux/binfmts.h
• linux/init.h
• linux/file.h
• linux/err.h
• linux/fs.h

Detected Declarations

• function Copyright
• function load_script
• function init_script_binfmt
• function exit_script_binfmt
• module init init_script_binfmt

Annotated Snippet

core_initcall(init_script_binfmt);
module_exit(exit_script_binfmt);
MODULE_DESCRIPTION("Kernel support for scripts starting with #!");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/string.h`, `linux/stat.h`, `linux/binfmts.h`, `linux/init.h`, `linux/file.h`, `linux/err.h`, `linux/fs.h`.
• Detected declarations: `function Copyright`, `function load_script`, `function init_script_binfmt`, `function exit_script_binfmt`, `module init init_script_binfmt`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• 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.