From: Luis Chamberlain <mcgrof@kernel.org>
To: menglong8.dong@gmail.com
Cc: viro@zeniv.linux.org.uk, keescook@chromium.org,
samitolvanen@google.com, johan@kernel.org, ojeda@kernel.org,
jeyu@kernel.org, joe@perches.com, dong.menglong@zte.com.cn,
masahiroy@kernel.org, jack@suse.cz, axboe@kernel.dk,
hare@suse.de, gregkh@linuxfoundation.org, tj@kernel.org,
song@kernel.org, neilb@suse.de, akpm@linux-foundation.org,
brho@google.com, f.fainelli@gmail.com,
wangkefeng.wang@huawei.com, arnd@arndb.de,
linux@rasmusvillemoes.dk, mhiramat@kernel.org,
rostedt@goodmis.org, vbabka@suse.cz, glider@google.com,
pmladek@suse.com, ebiederm@xmission.com, jojing64@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCH 3/3] init/do_mounts.c: fix rootfs_fs_type with ramfs
Date: Tue, 25 May 2021 00:52:56 +0000 [thread overview]
Message-ID: <20210525005256.GF4332@42.do-not-panic.com> (raw)
In-Reply-To: <20210522113155.244796-4-dong.menglong@zte.com.cn>
On Sat, May 22, 2021 at 07:31:55PM +0800, menglong8.dong@gmail.com wrote:
> From: Menglong Dong <dong.menglong@zte.com.cn>
>
> As for the existence of 'user root' which is introduced in previous
> patch, 'rootfs_fs_type', which is used as the root of mount tree,
> is not used directly any more. So it make no sense to switch it
> between ramfs and tmpfs, just fix it with ramfs to simplify the
> code.
You also noted this could be arbitrary. I don't see why its true that
the context used for init_mount_tree() can be arbitrary. And if it can
be, then why remove it / replace it with something more NULL like?
Luis
> Signed-off-by: Menglong Dong <dong.menglong@zte.com.cn>
> ---
> fs/namespace.c | 2 --
> include/linux/init.h | 1 -
> init/do_mounts.c | 18 +-----------------
> 3 files changed, 1 insertion(+), 20 deletions(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index f63337828e1c..8d2b57938e3a 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -17,7 +17,6 @@
> #include <linux/security.h>
> #include <linux/cred.h>
> #include <linux/idr.h>
> -#include <linux/init.h> /* init_rootfs */
> #include <linux/fs_struct.h> /* get_fs_root et.al. */
> #include <linux/fsnotify.h> /* fsnotify_vfsmount_delete */
> #include <linux/file.h>
> @@ -4241,7 +4240,6 @@ void __init mnt_init(void)
> if (!fs_kobj)
> printk(KERN_WARNING "%s: kobj create error\n", __func__);
> shmem_init();
> - init_rootfs();
> init_mount_tree();
> }
>
> diff --git a/include/linux/init.h b/include/linux/init.h
> index 045ad1650ed1..86bd92bb9550 100644
> --- a/include/linux/init.h
> +++ b/include/linux/init.h
> @@ -148,7 +148,6 @@ extern unsigned int reset_devices;
> /* used by init/main.c */
> void setup_arch(char **);
> void prepare_namespace(void);
> -void __init init_rootfs(void);
> extern struct file_system_type rootfs_fs_type;
>
> #if defined(CONFIG_STRICT_KERNEL_RWX) || defined(CONFIG_STRICT_MODULE_RWX)
> diff --git a/init/do_mounts.c b/init/do_mounts.c
> index 943cb58846fb..6d1253f75bb0 100644
> --- a/init/do_mounts.c
> +++ b/init/do_mounts.c
> @@ -689,24 +689,8 @@ void __init init_user_rootfs(void)
> }
> }
>
> -static bool is_tmpfs;
> -static int rootfs_init_fs_context(struct fs_context *fc)
> -{
> - if (IS_ENABLED(CONFIG_TMPFS) && is_tmpfs)
> - return shmem_init_fs_context(fc);
> -
> - return ramfs_init_fs_context(fc);
> -}
> -
> struct file_system_type rootfs_fs_type = {
> .name = "rootfs",
> - .init_fs_context = rootfs_init_fs_context,
> + .init_fs_context = ramfs_init_fs_context,
> .kill_sb = kill_litter_super,
> };
You mentioned
> -
> -void __init init_rootfs(void)
> -{
> - if (IS_ENABLED(CONFIG_TMPFS) && !saved_root_name[0] &&
> - (!root_fs_names || strstr(root_fs_names, "tmpfs")))
> - is_tmpfs = true;
> -}
> --
> 2.31.1
>
prev parent reply other threads:[~2021-05-25 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 11:31 [PATCH 0/3] init/initramfs.c: make initramfs support pivot_root menglong8.dong
2021-05-22 11:31 ` [PATCH 1/3] init/main.c: introduce function ramdisk_exec_exist() menglong8.dong
2021-05-25 1:02 ` Josh Triplett
2021-05-25 3:43 ` Menglong Dong
2021-05-25 8:04 ` Menglong Dong
2021-05-22 11:31 ` [PATCH 2/3] init/do_cmounts.c: introduce 'user_root' for initramfs menglong8.dong
2021-05-25 0:44 ` Luis Chamberlain
2021-05-25 3:28 ` Menglong Dong
2021-05-22 11:31 ` [PATCH 3/3] init/do_mounts.c: fix rootfs_fs_type with ramfs menglong8.dong
2021-05-24 21:47 ` Luis Chamberlain
2021-05-25 0:52 ` Luis Chamberlain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210525005256.GF4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=brho@google.com \
--cc=dong.menglong@zte.com.cn \
--cc=ebiederm@xmission.com \
--cc=f.fainelli@gmail.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=jeyu@kernel.org \
--cc=joe@perches.com \
--cc=johan@kernel.org \
--cc=jojing64@gmail.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=masahiroy@kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=neilb@suse.de \
--cc=ojeda@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.