fs/gfs2/xattr.h

File Facts

System

Linux kernel

Corpus path

fs/gfs2/xattr.h

Extension

.h

Size

1935 bytes

Lines

64

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 gfs2_inode
• struct iattr
• struct gfs2_ea_request
• struct gfs2_ea_location

Annotated Snippet

struct gfs2_ea_request {
	const char *er_name;
	char *er_data;
	unsigned int er_name_len;
	unsigned int er_data_len;
	unsigned int er_type; /* GFS2_EATYPE_... */
};

struct gfs2_ea_location {
	struct buffer_head *el_bh;
	struct gfs2_ea_header *el_ea;
	struct gfs2_ea_header *el_prev;
};

int __gfs2_xattr_set(struct inode *inode, const char *name,
		     const void *value, size_t size,
		     int flags, int type);
ssize_t gfs2_listxattr(struct dentry *dentry, char *buffer, size_t size);
int gfs2_ea_dealloc(struct gfs2_inode *ip, bool initialized);

/* Exported to acl.c */

int gfs2_xattr_acl_get(struct gfs2_inode *ip, const char *name, char **data);

#endif /* __EATTR_DOT_H__ */

Annotation

• Detected declarations: `struct gfs2_inode`, `struct iattr`, `struct gfs2_ea_request`, `struct gfs2_ea_location`.
• 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.