fs/quota/compat.h

File Facts

System

Linux kernel

Corpus path

fs/quota/compat.h

Extension

.h

Size

811 bytes

Lines

35

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/compat.h

Detected Declarations

• struct compat_if_dqblk
• struct compat_fs_qfilestat
• struct compat_fs_quota_stat

Annotated Snippet

struct compat_if_dqblk {
	compat_u64			dqb_bhardlimit;
	compat_u64			dqb_bsoftlimit;
	compat_u64			dqb_curspace;
	compat_u64			dqb_ihardlimit;
	compat_u64			dqb_isoftlimit;
	compat_u64			dqb_curinodes;
	compat_u64			dqb_btime;
	compat_u64			dqb_itime;
	compat_uint_t			dqb_valid;
};

struct compat_fs_qfilestat {
	compat_u64			dqb_bhardlimit;
	compat_u64			qfs_nblks;
	compat_uint_t			qfs_nextents;
};

struct compat_fs_quota_stat {
	__s8				qs_version;
	__u16				qs_flags;
	__s8				qs_pad;
	struct compat_fs_qfilestat	qs_uquota;
	struct compat_fs_qfilestat	qs_gquota;
	compat_uint_t			qs_incoredqs;
	compat_int_t			qs_btimelimit;
	compat_int_t			qs_itimelimit;
	compat_int_t			qs_rtbtimelimit;
	__u16				qs_bwarnlimit;
	__u16				qs_iwarnlimit;
};

Annotation

• Immediate include surface: `linux/compat.h`.
• Detected declarations: `struct compat_if_dqblk`, `struct compat_fs_qfilestat`, `struct compat_fs_quota_stat`.
• 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.