fs/xfs/libxfs/xfs_metadir.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/libxfs/xfs_metadir.h

Extension

.h

Size

1292 bytes

Lines

48

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 xfs_metadir_update

Annotated Snippet

struct xfs_metadir_update {
	/* Parent directory */
	struct xfs_inode	*dp;

	/* Path to metadata file */
	const char		*path;

	/* Parent pointer update context */
	struct xfs_parent_args	*ppargs;

	/* Child metadata file */
	struct xfs_inode	*ip;

	struct xfs_trans	*tp;

	enum xfs_metafile_type	metafile_type;

	unsigned int		dp_locked:1;
	unsigned int		ip_locked:1;
};

int xfs_metadir_load(struct xfs_trans *tp, struct xfs_inode *dp,
		const char *path, enum xfs_metafile_type metafile_type,
		struct xfs_inode **ipp);

int xfs_metadir_start_create(struct xfs_metadir_update *upd);
int xfs_metadir_create(struct xfs_metadir_update *upd, umode_t mode);

int xfs_metadir_start_link(struct xfs_metadir_update *upd);
int xfs_metadir_link(struct xfs_metadir_update *upd);

int xfs_metadir_commit(struct xfs_metadir_update *upd);
void xfs_metadir_cancel(struct xfs_metadir_update *upd, int error);

int xfs_metadir_mkdir(struct xfs_inode *dp, const char *path,
		struct xfs_inode **ipp);

#endif /* __XFS_METADIR_H__ */

Annotation

• Detected declarations: `struct xfs_metadir_update`.
• 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.