kernel.git/fs/ramfs/inode.c, branch linux-6.10.y

ramfs: Initialize security of in-memory inodes

2024-01-26T17:08:16Z

Add a call security_inode_init_security() after ramfs_get_inode(), to let LSMs initialize the inode security field. Skip ramfs_fill_super(), as the initialization is done through the sb_set_mnt_opts hook. Calling security_inode_init_security() call inside ramfs_get_inode() is not possible since, for CONFIG_SHMEM=n, tmpfs also calls the former after the latter. Pass NULL as initxattrs() callback to security_inode_init_security(), since the purpose of the call is only to initialize the in-memory inodes. Cc: Hugh Dickins Acked-by: Andrew Morton Signed-off-by: Roberto Sassu Signed-off-by: Casey Schaufler

ramfs: convert to new timestamp accessors

2023-10-18T12:08:26Z

Convert to using the new inode timestamp accessor functions. Signed-off-by: Jeff Layton Link: https://lore.kernel.org/r/20231004185347.80880-63-jlayton@kernel.org Signed-off-by: Christian Brauner

ramfs: convert to ctime accessor functions

2023-07-24T08:30:04Z

In later patches, we're going to change how the inode's ctime field is used. Switch to using accessor functions instead of raw accesses of inode->i_ctime. Signed-off-by: Jeff Layton Reviewed-by: Jan Kara Message-Id: <20230705190309.579783-69-jlayton@kernel.org> Signed-off-by: Christian Brauner

shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs

2023-06-19T23:19:04Z

As the ramfs-based tmpfs uses ramfs_init_fs_context() for the init_fs_context method, which allocates fc->s_fs_info, use ramfs_kill_sb() to free it and avoid a memory leak. Link: https://lkml.kernel.org/r/20230607161523.2876433-1-roberto.sassu@huaweicloud.com Fixes: c3b1b1cbf002 ("ramfs: add support for "mode=" mount option") Signed-off-by: Roberto Sassu Cc: Hugh Dickins Cc: David Howells Cc: Al Viro Cc: Signed-off-by: Andrew Morton

fs: port inode_init_owner() to mnt_idmap

2023-01-19T08:24:28Z

Convert to struct mnt_idmap. Last cycle we merged the necessary infrastructure in 256c8aed2b42 ("fs: introduce dedicated idmap type for mounts"). This is just the conversion to struct mnt_idmap. Currently we still pass around the plain namespace that was attached to a mount. This is in general pretty convenient but it makes it easy to conflate namespaces that are relevant on the filesystem with namespaces that are relevent on the mount level. Especially for non-vfs developers without detailed knowledge in this area this can be a potential source for bugs. Once the conversion to struct mnt_idmap is done all helpers down to the really low-level helpers will take a struct mnt_idmap argument instead of two namespace arguments. This way it becomes impossible to conflate the two eliminating the possibility of any bugs. All of the vfs and all filesystems only operate on struct mnt_idmap. Acked-by: Dave Chinner Reviewed-by: Christoph Hellwig Signed-off-by: Christian Brauner (Microsoft)

fs: port ->tmpfile() to pass mnt_idmap

2023-01-19T08:24:27Z

fs: port ->mknod() to pass mnt_idmap

2023-01-19T08:24:26Z

fs: port ->mkdir() to pass mnt_idmap

2023-01-19T08:24:26Z

fs: port ->symlink() to pass mnt_idmap

2023-01-19T08:24:25Z

fs: port ->create() to pass mnt_idmap

2023-01-19T08:24:25Z