fs/xfs/xfs_dquot_item.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/xfs_dquot_item.h

Extension

.h

Size

694 bytes

Lines

29

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_dquot
• struct xfs_trans
• struct xfs_mount
• struct xfs_dq_logitem

Annotated Snippet

struct xfs_dq_logitem {
	struct xfs_log_item	qli_item;	/* common portion */
	struct xfs_dquot	*qli_dquot;	/* dquot ptr */
	xfs_lsn_t		qli_flush_lsn;	/* lsn at last flush */

	/*
	 * We use this spinlock to coordinate access to the li_buf pointer in
	 * the log item and the qli_dirty flag.
	 */
	spinlock_t		qli_lock;
	bool			qli_dirty;	/* dirtied since last flush? */
};

void xfs_qm_dquot_logitem_init(struct xfs_dquot *dqp);

#endif	/* __XFS_DQUOT_ITEM_H__ */

Annotation

• Detected declarations: `struct xfs_dquot`, `struct xfs_trans`, `struct xfs_mount`, `struct xfs_dq_logitem`.
• 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.