fs/btrfs/acl.h

File Facts

System

Linux kernel

Corpus path

fs/btrfs/acl.h

Extension

.h

Size

819 bytes

Lines

41

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

Detected Declarations

• struct posix_acl
• struct inode
• struct btrfs_trans_handle
• struct mnt_idmap
• struct dentry
• struct btrfs_trans_handle
• function __btrfs_set_acl

Annotated Snippet

#ifndef BTRFS_ACL_H
#define BTRFS_ACL_H

#include <linux/types.h>

struct posix_acl;
struct inode;
struct btrfs_trans_handle;

#ifdef CONFIG_BTRFS_FS_POSIX_ACL

struct mnt_idmap;
struct dentry;

struct posix_acl *btrfs_get_acl(struct inode *inode, int type, bool rcu);
int btrfs_set_acl(struct mnt_idmap *idmap, struct dentry *dentry,
		  struct posix_acl *acl, int type);
int __btrfs_set_acl(struct btrfs_trans_handle *trans, struct inode *inode,
		    struct posix_acl *acl, int type);

#else

#include <linux/errno.h>

struct btrfs_trans_handle;

#define btrfs_get_acl NULL
#define btrfs_set_acl NULL
static inline int __btrfs_set_acl(struct btrfs_trans_handle *trans,
				  struct inode *inode, struct posix_acl *acl,
				  int type)
{
	return -EOPNOTSUPP;
}

#endif

#endif

Annotation

• Immediate include surface: `linux/types.h`, `linux/errno.h`.
• Detected declarations: `struct posix_acl`, `struct inode`, `struct btrfs_trans_handle`, `struct mnt_idmap`, `struct dentry`, `struct btrfs_trans_handle`, `function __btrfs_set_acl`.
• 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.