fs/xfs/scrub/fsb_bitmap.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/scrub/fsb_bitmap.h

Extension

.h

Size

911 bytes

Lines

38

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 xfsb_bitmap
• function xfsb_bitmap_init
• function xfsb_bitmap_destroy
• function xfsb_bitmap_set
• function xfsb_bitmap_walk

Annotated Snippet

struct xfsb_bitmap {
	struct xbitmap64	fsbitmap;
};

static inline void xfsb_bitmap_init(struct xfsb_bitmap *bitmap)
{
	xbitmap64_init(&bitmap->fsbitmap);
}

static inline void xfsb_bitmap_destroy(struct xfsb_bitmap *bitmap)
{
	xbitmap64_destroy(&bitmap->fsbitmap);
}

static inline int xfsb_bitmap_set(struct xfsb_bitmap *bitmap,
		xfs_fsblock_t start, xfs_filblks_t len)
{
	return xbitmap64_set(&bitmap->fsbitmap, start, len);
}

static inline int xfsb_bitmap_walk(struct xfsb_bitmap *bitmap,
		xbitmap64_walk_fn fn, void *priv)
{
	return xbitmap64_walk(&bitmap->fsbitmap, fn, priv);
}

#endif	/* __XFS_SCRUB_FSB_BITMAP_H__ */

Annotation

• Detected declarations: `struct xfsb_bitmap`, `function xfsb_bitmap_init`, `function xfsb_bitmap_destroy`, `function xfsb_bitmap_set`, `function xfsb_bitmap_walk`.
• 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.