linux-toradex.git/init/do_mounts.c, branch v3.12-rc5

initmpfs: use initramfs if rootfstype= or root= specified

2013-09-11T22:59:38+00:00

Command line option rootfstype=ramfs to obtain old initramfs behavior, and
use ramfs instead of tmpfs for stub when root= defined (for cosmetic
reasons).

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Rob Landley 
Cc: Jeff Layton 
Cc: Jens Axboe 
Cc: Stephen Warren 
Cc: Rusty Russell 
Cc: Jim Cromie 
Cc: Sam Ravnborg 
Cc: Greg Kroah-Hartman 
Cc: "Eric W. Biederman" 
Cc: Alexander Viro 
Cc: "H. Peter Anvin" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

initmpfs: make rootfs use tmpfs when CONFIG_TMPFS enabled

2013-09-11T22:59:37+00:00

Conditionally call the appropriate fs_init function and fill_super
functions.  Add a use once guard to shmem_init() to simply succeed on a
second call.

(Note that IS_ENABLED() is a compile time constant so dead code
elimination removes unused function calls when CONFIG_TMPFS is disabled.)

Signed-off-by: Rob Landley 
Cc: Jeff Layton 
Cc: Jens Axboe 
Cc: Stephen Warren 
Cc: Rusty Russell 
Cc: Jim Cromie 
Cc: Sam Ravnborg 
Cc: Greg Kroah-Hartman 
Cc: "Eric W. Biederman" 
Cc: Alexander Viro 
Cc: "H. Peter Anvin" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

initmpfs: move rootfs code from fs/ramfs/ to init/

2013-09-11T22:59:37+00:00

When the rootfs code was a wrapper around ramfs, having them in the same
file made sense.  Now that it can wrap another filesystem type, move it in
with the init code instead.

This also allows a subsequent patch to access rootfstype= command line
arg.

Signed-off-by: Rob Landley 
Cc: Jeff Layton 
Cc: Jens Axboe 
Cc: Stephen Warren 
Cc: Rusty Russell 
Cc: Jim Cromie 
Cc: Sam Ravnborg 
Cc: Greg Kroah-Hartman 
Cc: "Eric W. Biederman" 
Cc: Alexander Viro 
Cc: "H. Peter Anvin" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

insert missing space in printk line of root_delay

2013-07-03T23:07:45+00:00

Trivial, but it really looks better.

Signed-off-by: Toralf Förster 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

driver-core: constify data for class_find_device()

2013-02-06T20:18:56+00:00

All in-kernel users of class_find_device() don't really need mutable
data for match callback.

In two places (kernel/power/suspend_test.c, drivers/scsi/osd/osd_uld.c)
this patch changes match callbacks to use const search data.

The const is propagated to rtc_class_open() and power_supply_get_by_name()
parameters.

Note that there's a dev reference leak in suspend_test.c that's not
touched in this patch.

Signed-off-by: Michał Mirosław 
Acked-by: Grant Likely 
Signed-off-by: Greg Kroah-Hartman

block: partition: msdos: provide UUIDs for partitions

2012-11-23T13:28:58+00:00

The MSDOS/MBR partition table includes a 32-bit unique ID, often referred
to as the NT disk signature.  When combined with a partition number within
the table, this can form a unique ID similar in concept to EFI/GPT's
partition UUID.  Constructing and recording this value in struct
partition_meta_info allows MSDOS partitions to be referred to on the
kernel command-line using the following syntax:

root=PARTUUID=0002dd75-01

Signed-off-by: Stephen Warren 
Cc: Tejun Heo 
Cc: Will Drewry 
Cc: Kay Sievers 
Signed-off-by: Andrew Morton 
Signed-off-by: Jens Axboe

init: reduce PARTUUID min length to 1 from 36

2012-11-23T13:28:56+00:00

Reduce the minimum length for a root=PARTUUID= parameter to be considered
valid from 36 to 1.  EFI/GPT partition UUIDs are always exactly 36
characters long, hence the previous limit.  However, the next patch will
support DOS/MBR UUIDs too, which have a different, shorter, format.
Instead of validating any particular length, just ensure that at least
some non-empty value was given by the user.

Also, consider a missing UUID value to be a parsing error, in the same
vein as if /PARTNROFF exists and can't be parsed.  As such, make both
error cases print a message and disable rootwait.  Convert to pr_err while
we're at it.

Signed-off-by: Stephen Warren 
Cc: Tejun Heo 
Cc: Will Drewry 
Cc: Kay Sievers 
Signed-off-by: Andrew Morton 
Signed-off-by: Jens Axboe

block: store partition_meta_info.uuid as a string

2012-11-23T13:28:53+00:00

This will allow other types of UUID to be stored here, aside from true
UUIDs.  This also simplifies code that uses this field, since it's usually
constructed from a, used as a, or compared to other, strings.

Note: A simplistic approach here would be to set uuid_str[36]=0 whenever a
/PARTNROFF option was found to be present.  However, this modifies the
input string, and causes subsequent calls to devt_from_partuuid() not to
see the /PARTNROFF option, which causes different results.  In order to
avoid misleading future maintainers, this parameter is marked const.

Signed-off-by: Stephen Warren 
Cc: Tejun Heo 
Cc: Will Drewry 
Cc: Kay Sievers 
Signed-off-by: Andrew Morton 
Signed-off-by: Jens Axboe

vfs: allocate page instead of names_cache buffer in mount_block_root

2012-10-12T04:32:03+00:00

First, it's incorrect to call putname() after __getname_gfp() since the
bare __getname_gfp() call skips the auditing code, while putname()
doesn't.

mount_block_root allocates a PATH_MAX buffer via __getname_gfp, and then
calls get_fs_names to fill the buffer. That function can call
get_filesystem_list which assumes that that buffer is a full page in
size. On arches where PAGE_SIZE != 4k, then this could potentially
overrun.

In practice, it's hard to imagine the list of filesystem names even
approaching 4k, but it's best to be safe. Just allocate a page for this
purpose instead.

With this, we can also remove the __getname_gfp() definition since there
are no more callers.

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

init: disable sparse checking of the mount.o source files

2012-06-01T00:49:27+00:00

The init/mount.o source files produce a number of sparse warnings of the
type:

warning: incorrect type in argument 1 (different address spaces)
   expected char [noderef] *dev_name
   got char *name

This is due to the syscalls expecting some of the arguments to be user
pointers but they are being passed as kernel pointers.  This is harmless
but adds a lot of noise to a sparse build.

To limit the noise just disable the sparse checking in the relevant source
files, but still display a warning so that the user knows this has been
done.

Since the sparse checking has been disabled we can also remove the __user
__force casts that are scattered thru the source.

Signed-off-by: H Hartley Sweeten 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds