fs/xfs/xfs_filestream.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/xfs_filestream.h

Extension

.h

Size

708 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_mount
• struct xfs_inode
• struct xfs_bmalloca
• struct xfs_alloc_arg
• function xfs_inode_is_filestream

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
/*
 * Copyright (c) 2006-2007 Silicon Graphics, Inc.
 * All Rights Reserved.
 */
#ifndef __XFS_FILESTREAM_H__
#define __XFS_FILESTREAM_H__

struct xfs_mount;
struct xfs_inode;
struct xfs_bmalloca;
struct xfs_alloc_arg;

int xfs_filestream_mount(struct xfs_mount *mp);
void xfs_filestream_unmount(struct xfs_mount *mp);
void xfs_filestream_deassociate(struct xfs_inode *ip);
int xfs_filestream_select_ag(struct xfs_bmalloca *ap,
		struct xfs_alloc_arg *args, xfs_extlen_t *blen);

static inline int
xfs_inode_is_filestream(
	struct xfs_inode	*ip)
{
	return xfs_has_filestreams(ip->i_mount) ||
		(ip->i_diflags & XFS_DIFLAG_FILESTREAM);
}

#endif /* __XFS_FILESTREAM_H__ */

Annotation

• Detected declarations: `struct xfs_mount`, `struct xfs_inode`, `struct xfs_bmalloca`, `struct xfs_alloc_arg`, `function xfs_inode_is_filestream`.
• 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.