fs/xfs/xfs_exchmaps_item.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/xfs_exchmaps_item.h

Extension

.h

Size

2089 bytes

Lines

65

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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_mount
• struct kmem_cache
• struct xfs_xmi_log_item
• struct xfs_xmd_log_item
• struct xfs_exchmaps_intent

Annotated Snippet

struct xfs_xmi_log_item {
	struct xfs_log_item		xmi_item;
	atomic_t			xmi_refcount;
	struct xfs_xmi_log_format	xmi_format;
};

/*
 * This is the incore file mapping exchange done log item.  It is used to log
 * the fact that an exchange mentioned in an earlier xmi item have been
 * performed.
 */
struct xfs_xmd_log_item {
	struct xfs_log_item		xmd_item;
	struct xfs_xmi_log_item		*xmd_intent_log_item;
	struct xfs_xmd_log_format	xmd_format;
};

extern struct kmem_cache	*xfs_xmi_cache;
extern struct kmem_cache	*xfs_xmd_cache;

struct xfs_exchmaps_intent;

void xfs_exchmaps_defer_add(struct xfs_trans *tp,
		struct xfs_exchmaps_intent *xmi);

#endif	/* __XFS_EXCHMAPS_ITEM_H__ */

Annotation

• Detected declarations: `struct xfs_mount`, `struct kmem_cache`, `struct xfs_xmi_log_item`, `struct xfs_xmd_log_item`, `struct xfs_exchmaps_intent`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.