fs/nilfs2/ifile.h

File Facts

System

Linux kernel

Corpus path

fs/nilfs2/ifile.h

Extension

.h

Size

1117 bytes

Lines

44

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
• mdt.h
• alloc.h

Detected Declarations

• function Copyright
• function nilfs_ifile_unmap_inode

Annotated Snippet

#ifndef _NILFS_IFILE_H
#define _NILFS_IFILE_H

#include <linux/fs.h>
#include <linux/buffer_head.h>
#include "mdt.h"
#include "alloc.h"


static inline struct nilfs_inode *
nilfs_ifile_map_inode(struct inode *ifile, ino_t ino, struct buffer_head *ibh)
{
	size_t __offset_in_folio = nilfs_palloc_entry_offset(ifile, ino, ibh);

	return kmap_local_folio(ibh->b_folio, __offset_in_folio);
}

static inline void nilfs_ifile_unmap_inode(struct nilfs_inode *raw_inode)
{
	kunmap_local(raw_inode);
}

int nilfs_ifile_create_inode(struct inode *, ino_t *, struct buffer_head **);
int nilfs_ifile_delete_inode(struct inode *, ino_t);
int nilfs_ifile_get_inode_block(struct inode *, ino_t, struct buffer_head **);

int nilfs_ifile_count_free_inodes(struct inode *, u64 *, u64 *);

int nilfs_ifile_read(struct super_block *sb, struct nilfs_root *root,
		     __u64 cno, size_t inode_size);

#endif	/* _NILFS_IFILE_H */

Annotation

• Immediate include surface: `linux/fs.h`, `linux/buffer_head.h`, `mdt.h`, `alloc.h`.
• Detected declarations: `function Copyright`, `function nilfs_ifile_unmap_inode`.
• 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.