fs/btrfs/props.h
Source file repositories/reference/linux-study-clean/fs/btrfs/props.h
File Facts
- System
- Linux kernel
- Corpus path
fs/btrfs/props.h- Extension
.h- Size
- 903 bytes
- Lines
- 32
- 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/types.hlinux/compiler_types.h
Detected Declarations
struct btrfs_inodestruct btrfs_pathstruct btrfs_trans_handle
Annotated Snippet
#ifndef BTRFS_PROPS_H
#define BTRFS_PROPS_H
#include <linux/types.h>
#include <linux/compiler_types.h>
struct btrfs_inode;
struct btrfs_path;
struct btrfs_trans_handle;
int __init btrfs_props_init(void);
int btrfs_set_prop(struct btrfs_trans_handle *trans, struct btrfs_inode *inode,
const char *name, const char *value, size_t value_len,
int flags);
int btrfs_validate_prop(const struct btrfs_inode *inode, const char *name,
const char *value, size_t value_len);
bool btrfs_ignore_prop(const struct btrfs_inode *inode, const char *name);
int btrfs_load_inode_props(struct btrfs_inode *inode, struct btrfs_path *path);
int btrfs_inode_inherit_props(struct btrfs_trans_handle *trans,
struct btrfs_inode *inode,
const struct btrfs_inode *dir);
#endif
Annotation
- Immediate include surface: `linux/types.h`, `linux/compiler_types.h`.
- Detected declarations: `struct btrfs_inode`, `struct btrfs_path`, `struct btrfs_trans_handle`.
- 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.