fs/freevxfs/vxfs_fshead.h
Source file repositories/reference/linux-study-clean/fs/freevxfs/vxfs_fshead.h
File Facts
- System
- Linux kernel
- Corpus path
fs/freevxfs/vxfs_fshead.h- Extension
.h- Size
- 1193 bytes
- Lines
- 44
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct vxfs_fsh
Annotated Snippet
struct vxfs_fsh {
__fs32 fsh_version; /* fileset header version */
__fs32 fsh_fsindex; /* fileset index */
__fs32 fsh_time; /* modification time - sec */
__fs32 fsh_utime; /* modification time - usec */
__fs32 fsh_extop; /* extop flags */
__fs32 fsh_ninodes; /* allocated inodes */
__fs32 fsh_nau; /* number of IAUs */
__fs32 fsh_old_ilesize; /* old size of ilist */
__fs32 fsh_dflags; /* flags */
__fs32 fsh_quota; /* quota limit */
__fs32 fsh_maxinode; /* maximum inode number */
__fs32 fsh_iauino; /* IAU inode */
__fs32 fsh_ilistino[2]; /* ilist inodes */
__fs32 fsh_lctino; /* link count table inode */
/*
* Slightly more fields follow, but they
* a) are not of any interest for us, and
* b) differ a lot in different vxfs versions/ports
*/
};
#endif /* _VXFS_FSHEAD_H_ */
Annotation
- Detected declarations: `struct vxfs_fsh`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- 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.