2019-05-19 15:08:55 +03:00
// SPDX-License-Identifier: GPL-2.0-only
2005-04-17 02:20:36 +04:00
# include <linux/module.h>
# include <linux/sched.h>
# include <linux/ctype.h>
# include <linux/fd.h>
# include <linux/tty.h>
# include <linux/suspend.h>
# include <linux/root_dev.h>
# include <linux/security.h>
# include <linux/delay.h>
2005-07-13 00:58:07 +04:00
# include <linux/mount.h>
2006-07-18 21:59:59 +04:00
# include <linux/device.h>
2007-05-08 11:24:47 +04:00
# include <linux/init.h>
2008-02-06 12:36:47 +03:00
# include <linux/fs.h>
2008-07-25 12:45:29 +04:00
# include <linux/initrd.h>
2009-01-07 19:45:46 +03:00
# include <linux/async.h>
2009-03-30 03:50:06 +04:00
# include <linux/fs_struct.h>
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 11:04:11 +03:00
# include <linux/slab.h>
2013-09-12 01:26:10 +04:00
# include <linux/ramfs.h>
2013-09-12 01:26:12 +04:00
# include <linux/shmem_fs.h>
2023-08-13 11:23:49 +03:00
# include <linux/ktime.h>
2005-04-17 02:20:36 +04:00
# include <linux/nfs_fs.h>
# include <linux/nfs_fs_sb.h>
# include <linux/nfs_mount.h>
2020-06-07 17:18:59 +03:00
# include <linux/raid/detect.h>
2018-11-02 02:07:23 +03:00
# include <uapi/linux/mount.h>
2005-04-17 02:20:36 +04:00
# include "do_mounts.h"
[PATCH] vfs: MS_VERBOSE should be MS_SILENT
The meaning of MS_VERBOSE is backwards; if the bit is set, it really means,
"don't be verbose". This is confusing and counter-intuitive.
In addition, there is also no way to set the MS_VERBOSE flag in the
mount(8) program in util-linux, but interesting, it does define options
which would do the right thing if MS_SILENT were defined, which
unfortunately we do not:
#ifdef MS_SILENT
{ "quiet", 0, 0, MS_SILENT }, /* be quiet */
{ "loud", 0, 1, MS_SILENT }, /* print out messages. */
#endif
So the obvious fix is to deprecate the use of MS_VERBOSE and replace it
with MS_SILENT.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-24 14:15:10 +03:00
int root_mountflags = MS_RDONLY | MS_SILENT ;
2005-04-17 02:20:36 +04:00
static char __initdata saved_root_name [ 64 ] ;
2011-11-03 00:38:59 +04:00
static int root_wait ;
2005-04-17 02:20:36 +04:00
dev_t ROOT_DEV ;
static int __init load_ramdisk ( char * str )
{
2020-06-04 11:23:14 +03:00
pr_warn ( " ignoring the deprecated load_ramdisk= option \n " ) ;
2005-04-17 02:20:36 +04:00
return 1 ;
}
__setup ( " load_ramdisk= " , load_ramdisk ) ;
static int __init readonly ( char * str )
{
if ( * str )
return 0 ;
root_mountflags | = MS_RDONLY ;
return 1 ;
}
static int __init readwrite ( char * str )
{
if ( * str )
return 0 ;
root_mountflags & = ~ MS_RDONLY ;
return 1 ;
}
__setup ( " ro " , readonly ) ;
__setup ( " rw " , readwrite ) ;
static int __init root_dev_setup ( char * line )
{
2022-08-19 00:01:59 +03:00
strscpy ( saved_root_name , line , sizeof ( saved_root_name ) ) ;
2005-04-17 02:20:36 +04:00
return 1 ;
}
__setup ( " root= " , root_dev_setup ) ;
2007-07-16 10:40:35 +04:00
static int __init rootwait_setup ( char * str )
{
if ( * str )
return 0 ;
2023-08-13 11:23:49 +03:00
root_wait = - 1 ;
2007-07-16 10:40:35 +04:00
return 1 ;
}
__setup ( " rootwait " , rootwait_setup ) ;
2023-08-13 11:23:49 +03:00
static int __init rootwait_timeout_setup ( char * str )
{
int sec ;
if ( kstrtoint ( str , 0 , & sec ) | | sec < 0 ) {
pr_warn ( " ignoring invalid rootwait value \n " ) ;
goto ignore ;
}
if ( check_mul_overflow ( sec , MSEC_PER_SEC , & root_wait ) ) {
pr_warn ( " ignoring excessive rootwait value \n " ) ;
goto ignore ;
}
return 1 ;
ignore :
/* Fallback to indefinite wait */
root_wait = - 1 ;
return 1 ;
}
__setup ( " rootwait= " , rootwait_timeout_setup ) ;
2005-04-17 02:20:36 +04:00
static char * __initdata root_mount_data ;
static int __init root_data_setup ( char * str )
{
root_mount_data = str ;
return 1 ;
}
static char * __initdata root_fs_names ;
static int __init fs_names_setup ( char * str )
{
root_fs_names = str ;
return 1 ;
}
static unsigned int __initdata root_delay ;
static int __init root_delay_setup ( char * str )
{
root_delay = simple_strtoul ( str , NULL , 0 ) ;
return 1 ;
}
__setup ( " rootflags= " , root_data_setup ) ;
__setup ( " rootfstype= " , fs_names_setup ) ;
__setup ( " rootdelay= " , root_delay_setup ) ;
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
/* This can return zero length strings. Caller should check */
2023-05-20 10:23:32 +03:00
static int __init split_fs_names ( char * page , size_t size )
2005-04-17 02:20:36 +04:00
{
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
int count = 1 ;
2021-07-14 23:23:21 +03:00
char * p = page ;
2005-04-17 02:20:36 +04:00
2022-08-19 00:01:59 +03:00
strscpy ( p , root_fs_names , size ) ;
2021-07-14 23:23:21 +03:00
while ( * p + + ) {
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
if ( p [ - 1 ] = = ' , ' ) {
2021-07-14 23:23:21 +03:00
p [ - 1 ] = ' \0 ' ;
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
count + + ;
}
2005-04-17 02:20:36 +04:00
}
2021-07-14 23:23:19 +03:00
2021-07-14 23:23:21 +03:00
return count ;
2005-04-17 02:20:36 +04:00
}
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
static int __init do_mount_root ( const char * name , const char * fs ,
const int flags , const void * data )
2005-04-17 02:20:36 +04:00
{
2011-12-08 03:16:57 +04:00
struct super_block * s ;
2019-12-16 06:50:23 +03:00
struct page * p = NULL ;
char * data_page = NULL ;
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
int ret ;
2019-12-16 06:50:23 +03:00
if ( data ) {
2020-07-21 12:12:08 +03:00
/* init_mount() requires a full page as fifth argument */
2019-12-16 06:50:23 +03:00
p = alloc_page ( GFP_KERNEL ) ;
if ( ! p )
return - ENOMEM ;
data_page = page_address ( p ) ;
2020-07-21 12:12:08 +03:00
/* zero-pad. init_mount() will make sure it's terminated */
2019-12-16 06:50:23 +03:00
strncpy ( data_page , data , PAGE_SIZE ) ;
}
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
2020-07-21 12:12:08 +03:00
ret = init_mount ( name , " /root " , fs , flags , data_page ) ;
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
if ( ret )
goto out ;
2005-04-17 02:20:36 +04:00
2020-07-22 12:25:21 +03:00
init_chdir ( " /root " ) ;
2011-12-08 03:16:57 +04:00
s = current - > fs - > pwd . dentry - > d_sb ;
ROOT_DEV = s - > s_dev ;
2011-03-23 02:33:54 +03:00
printk ( KERN_INFO
" VFS: Mounted root (%s filesystem)%s on device %u:%u. \n " ,
2011-12-08 03:16:57 +04:00
s - > s_type - > name ,
2017-07-17 10:45:34 +03:00
sb_rdonly ( s ) ? " readonly " : " " ,
2011-12-08 03:16:57 +04:00
MAJOR ( ROOT_DEV ) , MINOR ( ROOT_DEV ) ) ;
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
out :
2019-12-16 06:50:23 +03:00
if ( p )
put_page ( p ) ;
init: use do_mount() instead of ksys_mount()
In prepare_namespace(), do_mount() can be used instead of ksys_mount()
as the first and third argument are const strings in the kernel, the
second and fourth argument are passed through anyway, and the fifth
argument is NULL.
In do_mount_root(), ksys_mount() is called with the first and third
argument being already kernelspace strings, which do not need to be
copied over from userspace to kernelspace (again). The second and
fourth arguments are passed through to do_mount() anyway. The fifth
argument, while already residing in kernelspace, needs to be put into
a page of its own. Then, do_mount() can be used instead of
ksys_mount().
Once this is done, there are no in-kernel users to ksys_mount() left,
which can therefore be removed.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
2018-10-23 23:41:09 +03:00
return ret ;
2005-04-17 02:20:36 +04:00
}
2023-05-31 15:55:19 +03:00
void __init mount_root_generic ( char * name , char * pretty_name , int flags )
2005-04-17 02:20:36 +04:00
{
2017-11-16 04:35:54 +03:00
struct page * page = alloc_page ( GFP_KERNEL ) ;
2012-10-10 23:25:26 +04:00
char * fs_names = page_address ( page ) ;
2005-04-17 02:20:36 +04:00
char * p ;
char b [ BDEVNAME_SIZE ] ;
2021-07-14 23:23:21 +03:00
int num_fs , i ;
2005-04-17 02:20:36 +04:00
2020-03-24 10:25:11 +03:00
scnprintf ( b , BDEVNAME_SIZE , " unknown-block(%u,%u) " ,
MAJOR ( ROOT_DEV ) , MINOR ( ROOT_DEV ) ) ;
2021-07-14 23:23:19 +03:00
if ( root_fs_names )
2023-05-20 10:23:32 +03:00
num_fs = split_fs_names ( fs_names , PAGE_SIZE ) ;
2021-07-14 23:23:19 +03:00
else
2021-07-14 23:23:21 +03:00
num_fs = list_bdev_fs_names ( fs_names , PAGE_SIZE ) ;
2005-04-17 02:20:36 +04:00
retry :
2021-07-14 23:23:21 +03:00
for ( i = 0 , p = fs_names ; i < num_fs ; i + + , p + = strlen ( p ) + 1 ) {
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
int err ;
if ( ! * p )
continue ;
err = do_mount_root ( name , p , flags , root_mount_data ) ;
2005-04-17 02:20:36 +04:00
switch ( err ) {
case 0 :
goto out ;
case - EACCES :
case - EINVAL :
continue ;
}
/*
* Allow the user to distinguish between failed sys_open
* and bad superblock on root device .
2007-05-09 13:33:24 +04:00
* and give them a list of the available devices
2005-04-17 02:20:36 +04:00
*/
2012-03-24 02:02:28 +04:00
printk ( " VFS: Cannot open root device \" %s \" or %s: error %d \n " ,
2023-05-31 15:55:19 +03:00
pretty_name , b , err ) ;
2007-05-09 13:33:24 +04:00
printk ( " Please append a correct \" root= \" boot option; here are the available partitions: \n " ) ;
printk_all_partitions ( ) ;
2023-05-18 06:53:21 +03:00
if ( root_fs_names )
num_fs = list_bdev_fs_names ( fs_names , PAGE_SIZE ) ;
if ( ! num_fs )
pr_err ( " Can't find any bdev filesystem to be used for mount! \n " ) ;
else {
pr_err ( " List of all bdev filesystems: \n " ) ;
for ( i = 0 , p = fs_names ; i < num_fs ; i + + , p + = strlen ( p ) + 1 )
pr_err ( " %s " , p ) ;
pr_err ( " \n " ) ;
}
2005-04-17 02:20:36 +04:00
panic ( " VFS: Unable to mount root fs on %s " , b ) ;
}
2017-07-17 10:45:35 +03:00
if ( ! ( flags & SB_RDONLY ) ) {
flags | = SB_RDONLY ;
2014-11-20 18:08:59 +03:00
goto retry ;
}
2006-05-15 20:44:29 +04:00
2007-05-09 13:33:24 +04:00
printk ( " List of all partitions: \n " ) ;
printk_all_partitions ( ) ;
2006-05-15 20:44:29 +04:00
printk ( " No filesystem could mount root, tried: " ) ;
2021-07-14 23:23:21 +03:00
for ( i = 0 , p = fs_names ; i < num_fs ; i + + , p + = strlen ( p ) + 1 )
2006-05-15 20:44:29 +04:00
printk ( " %s " , p ) ;
printk ( " \n " ) ;
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-09-30 22:45:40 +04:00
panic ( " VFS: Unable to mount root fs on %s " , b ) ;
2005-04-17 02:20:36 +04:00
out :
2012-10-10 23:25:26 +04:00
put_page ( page ) ;
2005-04-17 02:20:36 +04:00
}
# ifdef CONFIG_ROOT_NFS
2011-12-06 00:40:30 +04:00
# define NFSROOT_TIMEOUT_MIN 5
# define NFSROOT_TIMEOUT_MAX 30
# define NFSROOT_RETRY_MAX 5
2023-05-31 15:55:18 +03:00
static void __init mount_nfs_root ( void )
2005-04-17 02:20:36 +04:00
{
2010-09-17 18:54:37 +04:00
char * root_dev , * root_data ;
2011-12-06 00:40:30 +04:00
unsigned int timeout ;
2023-05-31 15:55:18 +03:00
int try ;
2005-04-17 02:20:36 +04:00
2023-05-31 15:55:18 +03:00
if ( nfs_root_data ( & root_dev , & root_data ) )
goto fail ;
2011-12-06 00:40:30 +04:00
/*
* The server or network may not be ready , so try several
* times . Stop after a few tries in case the client wants
* to fall back to other boot methods .
*/
timeout = NFSROOT_TIMEOUT_MIN ;
for ( try = 1 ; ; try + + ) {
2023-05-31 15:55:18 +03:00
if ( ! do_mount_root ( root_dev , " nfs " , root_mountflags , root_data ) )
return ;
2011-12-06 00:40:30 +04:00
if ( try > NFSROOT_RETRY_MAX )
break ;
/* Wait, in case the server refused us immediately */
ssleep ( timeout ) ;
timeout < < = 1 ;
if ( timeout > NFSROOT_TIMEOUT_MAX )
timeout = NFSROOT_TIMEOUT_MAX ;
}
2023-05-31 15:55:18 +03:00
fail :
pr_err ( " VFS: Unable to mount root fs via NFS. \n " ) ;
2005-04-17 02:20:36 +04:00
}
2023-05-31 15:55:18 +03:00
# else
static inline void mount_nfs_root ( void )
{
2005-04-17 02:20:36 +04:00
}
2023-05-31 15:55:18 +03:00
# endif /* CONFIG_ROOT_NFS */
2005-04-17 02:20:36 +04:00
2019-10-01 20:10:27 +03:00
# ifdef CONFIG_CIFS_ROOT
# define CIFSROOT_TIMEOUT_MIN 5
# define CIFSROOT_TIMEOUT_MAX 30
# define CIFSROOT_RETRY_MAX 5
2023-05-31 15:55:18 +03:00
static void __init mount_cifs_root ( void )
2019-10-01 20:10:27 +03:00
{
char * root_dev , * root_data ;
unsigned int timeout ;
2023-05-31 15:55:18 +03:00
int try ;
2019-10-01 20:10:27 +03:00
2023-05-31 15:55:18 +03:00
if ( cifs_root_data ( & root_dev , & root_data ) )
goto fail ;
2019-10-01 20:10:27 +03:00
timeout = CIFSROOT_TIMEOUT_MIN ;
for ( try = 1 ; ; try + + ) {
2023-05-31 15:55:18 +03:00
if ( ! do_mount_root ( root_dev , " cifs " , root_mountflags ,
root_data ) )
return ;
2019-10-01 20:10:27 +03:00
if ( try > CIFSROOT_RETRY_MAX )
break ;
ssleep ( timeout ) ;
timeout < < = 1 ;
if ( timeout > CIFSROOT_TIMEOUT_MAX )
timeout = CIFSROOT_TIMEOUT_MAX ;
}
2023-05-31 15:55:18 +03:00
fail :
pr_err ( " VFS: Unable to mount root fs via SMB. \n " ) ;
2019-10-01 20:10:27 +03:00
}
2023-05-31 15:55:18 +03:00
# else
static inline void mount_cifs_root ( void )
{
}
# endif /* CONFIG_CIFS_ROOT */
2019-10-01 20:10:27 +03:00
2021-07-14 23:23:20 +03:00
static bool __init fs_is_nodev ( char * fstype )
{
struct file_system_type * fs = get_fs_type ( fstype ) ;
bool ret = false ;
if ( fs ) {
ret = ! ( fs - > fs_flags & FS_REQUIRES_DEV ) ;
put_filesystem ( fs ) ;
}
return ret ;
}
2023-05-31 15:55:19 +03:00
static int __init mount_nodev_root ( char * root_device_name )
2021-07-14 23:23:20 +03:00
{
char * fs_names , * fstype ;
int err = - EINVAL ;
2021-07-14 23:23:21 +03:00
int num_fs , i ;
2021-07-14 23:23:20 +03:00
fs_names = ( void * ) __get_free_page ( GFP_KERNEL ) ;
if ( ! fs_names )
return - EINVAL ;
2023-05-20 10:23:32 +03:00
num_fs = split_fs_names ( fs_names , PAGE_SIZE ) ;
2021-07-14 23:23:20 +03:00
2021-07-14 23:23:21 +03:00
for ( i = 0 , fstype = fs_names ; i < num_fs ;
i + + , fstype + = strlen ( fstype ) + 1 ) {
init/do_mounts.c: Harden split_fs_names() against buffer overflow
split_fs_names() currently takes comma separate list of filesystems
and converts it into individual filesystem strings. Pleaces these
strings in the input buffer passed by caller and returns number of
strings.
If caller manages to pass input string bigger than buffer, then we
can write beyond the buffer. Or if string just fits buffer, we will
still write beyond the buffer as we append a '\0' byte at the end.
Pass size of input buffer to split_fs_names() and put enough checks
in place so such buffer overrun possibilities do not occur.
This patch does few things.
- Add a parameter "size" to split_fs_names(). This specifies size
of input buffer.
- Use strlcpy() (instead of strcpy()) so that we can't go beyond
buffer size. If input string "names" is larger than passed in
buffer, input string will be truncated to fit in buffer.
- Stop appending extra '\0' character at the end and avoid one
possibility of going beyond the input buffer size.
- Do not use extra loop to count number of strings.
- Previously if one passed "rootfstype=foo,,bar", split_fs_names()
will return only 1 string "foo" (and "bar" will be truncated
due to extra ,). After this patch, now split_fs_names() will
return 3 strings ("foo", zero-sized-string, and "bar").
Callers of split_fs_names() have been modified to check for
zero sized string and skip to next one.
Reported-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2021-09-17 16:13:23 +03:00
if ( ! * fstype )
continue ;
2021-07-14 23:23:20 +03:00
if ( ! fs_is_nodev ( fstype ) )
continue ;
err = do_mount_root ( root_device_name , fstype , root_mountflags ,
root_mount_data ) ;
if ( ! err )
break ;
}
free_page ( ( unsigned long ) fs_names ) ;
return err ;
}
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-09-30 22:45:40 +04:00
# ifdef CONFIG_BLOCK
2023-05-31 15:55:19 +03:00
static void __init mount_block_root ( char * root_device_name )
2005-04-17 02:20:36 +04:00
{
2023-05-31 15:55:18 +03:00
int err = create_dev ( " /dev/root " , ROOT_DEV ) ;
if ( err < 0 )
pr_emerg ( " Failed to create /dev/root: %d \n " , err ) ;
2023-05-31 15:55:19 +03:00
mount_root_generic ( " /dev/root " , root_device_name , root_mountflags ) ;
2023-05-31 15:55:18 +03:00
}
# else
2023-05-31 15:55:19 +03:00
static inline void mount_block_root ( char * root_device_name )
2023-05-31 15:55:18 +03:00
{
}
# endif /* CONFIG_BLOCK */
2015-06-26 01:03:37 +03:00
2023-05-31 15:55:19 +03:00
void __init mount_root ( char * root_device_name )
2023-05-31 15:55:18 +03:00
{
switch ( ROOT_DEV ) {
case Root_NFS :
mount_nfs_root ( ) ;
break ;
case Root_CIFS :
mount_cifs_root ( ) ;
break ;
2023-05-31 15:55:21 +03:00
case Root_Generic :
mount_root_generic ( root_device_name , root_device_name ,
root_mountflags ) ;
break ;
2023-05-31 15:55:18 +03:00
case 0 :
2023-05-31 15:55:19 +03:00
if ( root_device_name & & root_fs_names & &
mount_nodev_root ( root_device_name ) = = 0 )
2023-05-31 15:55:18 +03:00
break ;
fallthrough ;
default :
2023-05-31 15:55:19 +03:00
mount_block_root ( root_device_name ) ;
2023-05-31 15:55:18 +03:00
break ;
2005-04-17 02:20:36 +04:00
}
}
2023-05-31 15:55:22 +03:00
/* wait for any asynchronous scanning to complete */
static void __init wait_for_root ( char * root_device_name )
{
2023-08-13 11:23:49 +03:00
ktime_t end ;
2023-05-31 15:55:22 +03:00
if ( ROOT_DEV ! = 0 )
2020-06-04 11:23:14 +03:00
return ;
2015-06-26 01:03:37 +03:00
2023-05-31 15:55:22 +03:00
pr_info ( " Waiting for root device %s... \n " , root_device_name ) ;
2023-08-13 11:23:49 +03:00
end = ktime_add_ms ( ktime_get_raw ( ) , root_wait ) ;
2023-05-31 15:55:24 +03:00
while ( ! driver_probe_done ( ) | |
2023-08-13 11:23:49 +03:00
early_lookup_bdev ( root_device_name , & ROOT_DEV ) < 0 ) {
2023-05-31 15:55:22 +03:00
msleep ( 5 ) ;
2023-08-13 11:23:49 +03:00
if ( root_wait > 0 & & ktime_after ( ktime_get_raw ( ) , end ) )
break ;
}
2023-05-31 15:55:22 +03:00
async_synchronize_full ( ) ;
}
2023-05-31 15:55:21 +03:00
static dev_t __init parse_root_device ( char * root_device_name )
{
2023-05-31 15:55:25 +03:00
int error ;
2023-05-31 15:55:24 +03:00
dev_t dev ;
2023-05-31 15:55:21 +03:00
if ( ! strncmp ( root_device_name , " mtd " , 3 ) | |
! strncmp ( root_device_name , " ubi " , 3 ) )
return Root_Generic ;
2023-05-31 15:55:23 +03:00
if ( strcmp ( root_device_name , " /dev/nfs " ) = = 0 )
return Root_NFS ;
if ( strcmp ( root_device_name , " /dev/cifs " ) = = 0 )
return Root_CIFS ;
if ( strcmp ( root_device_name , " /dev/ram " ) = = 0 )
return Root_RAM0 ;
2023-05-31 15:55:24 +03:00
2023-05-31 15:55:25 +03:00
error = early_lookup_bdev ( root_device_name , & dev ) ;
if ( error ) {
if ( error = = - EINVAL & & root_wait ) {
pr_err ( " Disabling rootwait; root= is invalid. \n " ) ;
root_wait = 0 ;
}
2023-05-31 15:55:24 +03:00
return 0 ;
2015-06-26 01:03:37 +03:00
}
2023-05-31 15:55:24 +03:00
return dev ;
2005-04-17 02:20:36 +04:00
}
/*
* Prepare the namespace - decide what / where to mount , load ramdisks , etc .
*/
void __init prepare_namespace ( void )
{
if ( root_delay ) {
2013-07-04 02:05:38 +04:00
printk ( KERN_INFO " Waiting %d sec before mounting root device... \n " ,
2005-04-17 02:20:36 +04:00
root_delay ) ;
ssleep ( root_delay ) ;
}
2009-02-14 03:59:06 +03:00
/*
* wait for the known devices to complete their probing
*
* Note : this is a potential source of long boot delays .
* For example , it is not atypical to wait 5 seconds here
* for the touchpad of a laptop to initialize .
*/
wait_for_device_probe ( ) ;
2006-07-18 21:59:59 +04:00
2005-04-17 02:20:36 +04:00
md_run_setup ( ) ;
2023-05-31 15:55:21 +03:00
if ( saved_root_name [ 0 ] )
ROOT_DEV = parse_root_device ( saved_root_name ) ;
2005-04-17 02:20:36 +04:00
2023-05-31 15:55:20 +03:00
if ( initrd_load ( saved_root_name ) )
2005-04-17 02:20:36 +04:00
goto out ;
2023-05-31 15:55:22 +03:00
if ( root_wait )
wait_for_root ( saved_root_name ) ;
2023-05-31 15:55:20 +03:00
mount_root ( saved_root_name ) ;
2005-04-17 02:20:36 +04:00
out :
2018-10-23 23:10:35 +03:00
devtmpfs_mount ( ) ;
2020-07-21 12:12:08 +03:00
init_mount ( " . " , " / " , NULL , MS_MOVE , NULL ) ;
2020-07-22 12:26:13 +03:00
init_chroot ( " . " ) ;
2005-04-17 02:20:36 +04:00
}
2013-09-12 01:26:10 +04:00
2013-09-12 01:26:13 +04:00
static bool is_tmpfs ;
vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs to use the new mount API
Convert the ramfs, shmem, tmpfs, devtmpfs and rootfs filesystems to the new
internal mount API as the old one will be obsoleted and removed. This
allows greater flexibility in communication of mount parameters between
userspace, the VFS and the filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Note that tmpfs is slightly tricky as it can contain embedded commas, so it
can't be trivially split up using strsep() to break on commas in
generic_parse_monolithic(). Instead, tmpfs has to supply its own generic
parser.
However, if tmpfs changes, then devtmpfs and rootfs, which are wrappers
around tmpfs or ramfs, must change too - and thus so must ramfs, so these
had to be converted also.
[AV: rewritten]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Hugh Dickins <hughd@google.com>
cc: linux-mm@kvack.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2019-03-25 19:38:31 +03:00
static int rootfs_init_fs_context ( struct fs_context * fc )
2013-09-12 01:26:10 +04:00
{
2013-09-12 01:26:13 +04:00
if ( IS_ENABLED ( CONFIG_TMPFS ) & & is_tmpfs )
vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs to use the new mount API
Convert the ramfs, shmem, tmpfs, devtmpfs and rootfs filesystems to the new
internal mount API as the old one will be obsoleted and removed. This
allows greater flexibility in communication of mount parameters between
userspace, the VFS and the filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Note that tmpfs is slightly tricky as it can contain embedded commas, so it
can't be trivially split up using strsep() to break on commas in
generic_parse_monolithic(). Instead, tmpfs has to supply its own generic
parser.
However, if tmpfs changes, then devtmpfs and rootfs, which are wrappers
around tmpfs or ramfs, must change too - and thus so must ramfs, so these
had to be converted also.
[AV: rewritten]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Hugh Dickins <hughd@google.com>
cc: linux-mm@kvack.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2019-03-25 19:38:31 +03:00
return shmem_init_fs_context ( fc ) ;
2013-09-12 01:26:13 +04:00
vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs to use the new mount API
Convert the ramfs, shmem, tmpfs, devtmpfs and rootfs filesystems to the new
internal mount API as the old one will be obsoleted and removed. This
allows greater flexibility in communication of mount parameters between
userspace, the VFS and the filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Note that tmpfs is slightly tricky as it can contain embedded commas, so it
can't be trivially split up using strsep() to break on commas in
generic_parse_monolithic(). Instead, tmpfs has to supply its own generic
parser.
However, if tmpfs changes, then devtmpfs and rootfs, which are wrappers
around tmpfs or ramfs, must change too - and thus so must ramfs, so these
had to be converted also.
[AV: rewritten]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Hugh Dickins <hughd@google.com>
cc: linux-mm@kvack.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2019-03-25 19:38:31 +03:00
return ramfs_init_fs_context ( fc ) ;
2013-09-12 01:26:10 +04:00
}
2019-05-31 00:48:35 +03:00
struct file_system_type rootfs_fs_type = {
2013-09-12 01:26:10 +04:00
. name = " rootfs " ,
vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs to use the new mount API
Convert the ramfs, shmem, tmpfs, devtmpfs and rootfs filesystems to the new
internal mount API as the old one will be obsoleted and removed. This
allows greater flexibility in communication of mount parameters between
userspace, the VFS and the filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Note that tmpfs is slightly tricky as it can contain embedded commas, so it
can't be trivially split up using strsep() to break on commas in
generic_parse_monolithic(). Instead, tmpfs has to supply its own generic
parser.
However, if tmpfs changes, then devtmpfs and rootfs, which are wrappers
around tmpfs or ramfs, must change too - and thus so must ramfs, so these
had to be converted also.
[AV: rewritten]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Hugh Dickins <hughd@google.com>
cc: linux-mm@kvack.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2019-03-25 19:38:31 +03:00
. init_fs_context = rootfs_init_fs_context ,
2013-09-12 01:26:10 +04:00
. kill_sb = kill_litter_super ,
} ;
2019-06-02 01:09:44 +03:00
void __init init_rootfs ( void )
2013-09-12 01:26:10 +04:00
{
2013-09-12 01:26:13 +04:00
if ( IS_ENABLED ( CONFIG_TMPFS ) & & ! saved_root_name [ 0 ] & &
2019-06-02 01:09:44 +03:00
( ! root_fs_names | | strstr ( root_fs_names , " tmpfs " ) ) )
2013-09-12 01:26:13 +04:00
is_tmpfs = true ;
2013-09-12 01:26:10 +04:00
}
