fs/ramfs/inode.c
Source file repositories/reference/linux-study-clean/fs/ramfs/inode.c
File Facts
- System
- Linux kernel
- Corpus path
fs/ramfs/inode.c- Extension
.c- Size
- 7676 bytes
- Lines
- 330
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/fs.hlinux/pagemap.hlinux/highmem.hlinux/time.hlinux/init.hlinux/string.hlinux/backing-dev.hlinux/ramfs.hlinux/sched.hlinux/parser.hlinux/magic.hlinux/slab.hlinux/uaccess.hlinux/fs_context.hlinux/fs_parser.hlinux/seq_file.hinternal.h
Detected Declarations
struct ramfs_mount_optsstruct ramfs_fs_infoenum ramfs_paramfunction ramfs_mknodfunction ramfs_createfunction ramfs_symlinkfunction ramfs_tmpfilefunction ramfs_show_optionsfunction ramfs_parse_paramfunction ramfs_fill_superfunction ramfs_get_treefunction ramfs_free_fcfunction ramfs_init_fs_contextfunction ramfs_kill_sbfunction init_ramfs_fsmodule init init_ramfs_fs
Annotated Snippet
struct ramfs_mount_opts {
umode_t mode;
};
struct ramfs_fs_info {
struct ramfs_mount_opts mount_opts;
};
#define RAMFS_DEFAULT_MODE 0755
static const struct super_operations ramfs_ops;
static const struct inode_operations ramfs_dir_inode_operations;
struct inode *ramfs_get_inode(struct super_block *sb,
const struct inode *dir, umode_t mode, dev_t dev)
{
struct inode * inode = new_inode(sb);
if (inode) {
inode->i_ino = get_next_ino();
inode_init_owner(&nop_mnt_idmap, inode, dir, mode);
inode->i_mapping->a_ops = &ram_aops;
mapping_set_gfp_mask(inode->i_mapping, GFP_HIGHUSER);
mapping_set_unevictable(inode->i_mapping);
simple_inode_init_ts(inode);
switch (mode & S_IFMT) {
default:
init_special_inode(inode, mode, dev);
break;
case S_IFREG:
inode->i_op = &ramfs_file_inode_operations;
inode->i_fop = &ramfs_file_operations;
break;
case S_IFDIR:
inode->i_op = &ramfs_dir_inode_operations;
inode->i_fop = &simple_dir_operations;
/* directory inodes start off with i_nlink == 2 (for "." entry) */
inc_nlink(inode);
break;
case S_IFLNK:
inode->i_op = &page_symlink_inode_operations;
inode_nohighmem(inode);
break;
}
}
return inode;
}
/*
* File creation. Allocate an inode, and we're done..
*/
/* SMP-safe */
static int
ramfs_mknod(struct mnt_idmap *idmap, struct inode *dir,
struct dentry *dentry, umode_t mode, dev_t dev)
{
struct inode * inode = ramfs_get_inode(dir->i_sb, dir, mode, dev);
int error = -ENOSPC;
if (inode) {
error = security_inode_init_security(inode, dir,
&dentry->d_name, NULL,
NULL);
if (error) {
iput(inode);
goto out;
}
d_make_persistent(dentry, inode);
error = 0;
inode_set_mtime_to_ts(dir, inode_set_ctime_current(dir));
}
out:
return error;
}
static struct dentry *ramfs_mkdir(struct mnt_idmap *idmap, struct inode *dir,
struct dentry *dentry, umode_t mode)
{
int retval = ramfs_mknod(&nop_mnt_idmap, dir, dentry, mode | S_IFDIR, 0);
if (!retval)
inc_nlink(dir);
return ERR_PTR(retval);
}
static int ramfs_create(struct mnt_idmap *idmap, struct inode *dir,
struct dentry *dentry, umode_t mode, bool excl)
{
return ramfs_mknod(&nop_mnt_idmap, dir, dentry, mode | S_IFREG, 0);
Annotation
- Immediate include surface: `linux/fs.h`, `linux/pagemap.h`, `linux/highmem.h`, `linux/time.h`, `linux/init.h`, `linux/string.h`, `linux/backing-dev.h`, `linux/ramfs.h`.
- Detected declarations: `struct ramfs_mount_opts`, `struct ramfs_fs_info`, `enum ramfs_param`, `function ramfs_mknod`, `function ramfs_create`, `function ramfs_symlink`, `function ramfs_tmpfile`, `function ramfs_show_options`, `function ramfs_parse_param`, `function ramfs_fill_super`.
- 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.