fs/nls/nls_cp936.c
Source file repositories/reference/linux-study-clean/fs/nls/nls_cp936.c
File Facts
- System
- Linux kernel
- Corpus path
fs/nls/nls_cp936.c- Extension
.c- Size
- 698366 bytes
- Lines
- 11113
- 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.hlinux/kernel.hlinux/string.hlinux/nls.hlinux/errno.h
Detected Declarations
function uni2charfunction char2unifunction init_nls_cp936function exit_nls_cp936module init init_nls_cp936
Annotated Snippet
module_init(init_nls_cp936)
module_exit(exit_nls_cp936)
MODULE_DESCRIPTION("NLS Simplified Chinese charset (CP936, GB2312)");
MODULE_LICENSE("Dual BSD/GPL");
MODULE_ALIAS_NLS(gb2312);Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/string.h`, `linux/nls.h`, `linux/errno.h`.
- Detected declarations: `function uni2char`, `function char2uni`, `function init_nls_cp936`, `function exit_nls_cp936`, `module init init_nls_cp936`.
- 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.