fs/freevxfs/vxfs_olt.c

File Facts

System

Linux kernel

Corpus path

fs/freevxfs/vxfs_olt.c

Extension

.c

Size

2510 bytes

Lines

106

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/fs.h
• linux/buffer_head.h
• linux/kernel.h
• vxfs.h
• vxfs_olt.h
• vxfs_extern.h

Detected Declarations

• function Copyright
• function vxfs_get_ilist
• function vxfs_oblock
• function vxfs_read_olt

Annotated Snippet

switch (fs32_to_cpu(infp, ocp->olt_type)) {
		case VXFS_OLT_FSHEAD:
			vxfs_get_fshead((struct vxfs_oltfshead *)oaddr, infp);
			break;
		case VXFS_OLT_ILIST:
			vxfs_get_ilist((struct vxfs_oltilist *)oaddr, infp);
			break;
		}

		oaddr += fs32_to_cpu(infp, ocp->olt_size);
	}

	brelse(bp);
	return (infp->vsi_fshino && infp->vsi_iext) ? 0 : -EINVAL;

fail:
	brelse(bp);
	return -EINVAL;
}

Annotation

• Immediate include surface: `linux/fs.h`, `linux/buffer_head.h`, `linux/kernel.h`, `vxfs.h`, `vxfs_olt.h`, `vxfs_extern.h`.
• Detected declarations: `function Copyright`, `function vxfs_get_ilist`, `function vxfs_oblock`, `function vxfs_read_olt`.
• 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.