fs/overlayfs/params.h
Source file repositories/reference/linux-study-clean/fs/overlayfs/params.h
File Facts
- System
- Linux kernel
- Corpus path
fs/overlayfs/params.h- Extension
.h- Size
- 1093 bytes
- Lines
- 45
- 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
linux/fs_context.hlinux/fs_parser.h
Detected Declarations
struct ovl_fsstruct ovl_configstruct ovl_opt_setstruct ovl_fs_context_layerstruct ovl_fs_context
Annotated Snippet
struct ovl_opt_set {
bool metacopy;
bool redirect;
bool nfs_export;
bool index;
};
#define OVL_MAX_STACK 500
struct ovl_fs_context_layer {
char *name;
struct path path;
};
struct ovl_fs_context {
struct path upper;
struct path work;
size_t capacity;
size_t nr; /* includes nr_data */
size_t nr_data;
struct ovl_opt_set set;
struct ovl_fs_context_layer *lower;
char *lowerdir_all; /* user provided lowerdir string */
bool casefold_set;
};
int ovl_init_fs_context(struct fs_context *fc);
void ovl_free_fs(struct ovl_fs *ofs);
int ovl_fs_params_verify(const struct ovl_fs_context *ctx,
struct ovl_config *config);
int ovl_show_options(struct seq_file *m, struct dentry *dentry);
const char *ovl_xino_mode(struct ovl_config *config);
Annotation
- Immediate include surface: `linux/fs_context.h`, `linux/fs_parser.h`.
- Detected declarations: `struct ovl_fs`, `struct ovl_config`, `struct ovl_opt_set`, `struct ovl_fs_context_layer`, `struct ovl_fs_context`.
- 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.