fs/btrfs/verity.h

File Facts

System

Linux kernel

Corpus path

fs/btrfs/verity.h

Extension

.h

Size

633 bytes

Lines

36

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/fsverity.h
• linux/errno.h

Detected Declarations

• struct inode
• struct btrfs_inode
• function btrfs_drop_verity_items
• function btrfs_get_verity_descriptor

Annotated Snippet

#ifndef BTRFS_VERITY_H
#define BTRFS_VERITY_H

struct inode;
struct btrfs_inode;

#ifdef CONFIG_FS_VERITY

#include <linux/fsverity.h>

extern const struct fsverity_operations btrfs_verityops;

int btrfs_drop_verity_items(struct btrfs_inode *inode);
int btrfs_get_verity_descriptor(struct inode *inode, void *buf, size_t buf_size);

#else

#include <linux/errno.h>

static inline int btrfs_drop_verity_items(struct btrfs_inode *inode)
{
	return 0;
}

static inline int btrfs_get_verity_descriptor(struct inode *inode, void *buf,
					      size_t buf_size)
{
	return -EPERM;
}

#endif

#endif

Annotation

• Immediate include surface: `linux/fsverity.h`, `linux/errno.h`.
• Detected declarations: `struct inode`, `struct btrfs_inode`, `function btrfs_drop_verity_items`, `function btrfs_get_verity_descriptor`.
• 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.