fs/btrfs/xattr.h
Source file repositories/reference/linux-study-clean/fs/btrfs/xattr.h
File Facts
- System
- Linux kernel
- Corpus path
fs/btrfs/xattr.h- Extension
.h- Size
- 909 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.h
Detected Declarations
struct dentrystruct inodestruct qstrstruct xattr_handlerstruct btrfs_trans_handle
Annotated Snippet
#ifndef BTRFS_XATTR_H
#define BTRFS_XATTR_H
#include <linux/types.h>
struct dentry;
struct inode;
struct qstr;
struct xattr_handler;
struct btrfs_trans_handle;
extern const struct xattr_handler * const btrfs_xattr_handlers[];
int btrfs_getxattr(const struct inode *inode, const char *name,
void *buffer, size_t size);
int btrfs_setxattr(struct btrfs_trans_handle *trans, struct inode *inode,
const char *name, const void *value, size_t size, int flags);
int btrfs_setxattr_trans(struct inode *inode, const char *name,
const void *value, size_t size, int flags);
ssize_t btrfs_listxattr(struct dentry *dentry, char *buffer, size_t size);
int btrfs_xattr_security_init(struct btrfs_trans_handle *trans,
struct inode *inode, struct inode *dir,
const struct qstr *qstr);
#endif
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct dentry`, `struct inode`, `struct qstr`, `struct xattr_handler`, `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.