GitLab

* commit '4e830641':
  Prevent integer overflow when allocating native_handle_t

* commit '1def25a2':
  Prevent integer overflow when allocating native_handle_t

Change-Id: I671a57d906ca6826722fb892627d235b14b822eb

* commit '058ad0b6':
  Prevent integer overflow when allocating native_handle_t

* commit 'e8582d65':
  Prevent integer overflow when allocating native_handle_t

* commit '9bd7afc0':
  Prevent integer overflow when allocating native_handle_t

User specified values of numInts and numFds can overflow
and cause malloc to allocate less than we expect, causing
heap corruption in subsequent operations on the allocation.

Bug: 19334482
Change-Id: I43c75f536ea4c08f14ca12ca6288660fd2d1ec55

am 8b448629: am 16092b7a: Merge "fs_mgr: allow for zramsize to be specified as percentage of total memory" into lmp-mr1-dev

* commit '8b448629':
  fs_mgr: allow for zramsize to be specified as percentage of total memory

am 16092b7a: Merge "fs_mgr: allow for zramsize to be specified as percentage of total memory" into lmp-mr1-dev

* commit '16092b7a':
  fs_mgr: allow for zramsize to be specified as percentage of total memory

Change-Id: I6aa2ee2c4bf1802e5aa814374f9842a34179ffea

Modifies the code so that if the unwind fails, the code still prints
as much data as possible.

Also, for sibling threads, skip printing the maps and memory/code
since it's not likely to be very relevant.

Fix a few cases where extra space is at the end of lines.

Fix an inverted if statement that was checking the wrong condition.

Bug: 18816322
Bug: 20829534

(cherry picked from ab9e7dce)

Change-Id: If2d3a734724c23df4192f4dfc6bd69d6729fbc8d

If the zramsize entry has a % size at the end, as in the following example:

	/dev/block/zram0 none swap defaults zramsize=25%

then we will set the value as that percentage of total RAM, as read by scanning
/proc/meminfo.

b/20760266 Seed common build allocated too much for zRAM-backed swap

Change-Id: I17c91d311ba99ae7adae112bfe1b38542ea69b80
Signed-off-by: Iliyan Malchev <malchev@google.com>

* commit 'ecf184c9':
  init: get rid of the remaining double mounts

* commit '9c9280d8':
  init: get rid of the remaining double mounts

* commit '45a49d0e':
  init: use SELinux /dev/null if available

* commit 'ccac2be8':
  init: use SELinux /dev/null if available

Don't double mount /dev and its subdirectories anymore. Instead, the
first stage init is solely responsible for mounting it.

Don't have init prepare the property space. This is the responsibility
of the second stage init.

Don't have SELinux use the property space to determine how we should
be running. Instead, create a new function and extract the data we
need directly from /proc/cmdline. SELinux needs this information in
the first stage init process where the property service isn't available.

Change-Id: I5b4f3bec79463a7381a68f30bdda78b5cc122a96

SELinux provides it's own /dev/null character device at
/sys/fs/selinux/null. This character device is exactly the same
as /dev/null, including the same major/minor numbers, and can
be used wherever /dev/null is used.

Use /sys/fs/selinux/null instead of trying to create our own
/dev/__null__ device. This moves us one step closer to eliminating
all uses of mknod() by init.

/sys/fs/selinux/null is only available once the /sys/fs/selinux filesystem
is mounted. It's not available to the first stage init, so we
still have to fall back to mknod then.

Change-Id: Ic733767ea6220a130537de33cc478ae79578ce20

* commit 'b31c3a5a':
  init: don't double mount /proc and /sys

* commit '6b6df173':
  init: fix write_file checkreqprot logic error

* commit 'ecd6e36d':
  Improve logging of USBDEVFS_CLAIMINTERFACE failures.

* commit '178299fd':
  init: don't double mount /proc and /sys

* commit 'f8b0743e':
  init: fix write_file checkreqprot logic error

* commit '47a9ef2f':
  Improve logging of USBDEVFS_CLAIMINTERFACE failures.

The first stage init mounts /proc and /sys, and then the second
stage init also mounts /proc and /sys on top of the existing mount.
Only mount these two directories once, in the first stage init.

Not yet fixed: the double mounting of /dev. Removing the double
mounting doesn't work right now because both init stages are trying
to create a property space, and if the double mount of /dev goes away,
the property service in the second stage init fails to work.

Change-Id: I13719027a47526d074390c2b1a605ad99fb43a8f

write_file() returned -errno on error, not -1. Callers who check for
-1 would falsely believe that the write was successful when it wasn't.
Fixup write_file so that it return -1 on error consistent
with other functions.

Change-Id: Ic51aaf8678d8d97b2606bd171f11b3b11f642e39

Bug: https://code.google.com/p/android/issues/detail?id=170054
Change-Id: I9b11eb019093e3322da0a8e70d6e17de4c25ab75

* commit 'ecfb3664':
  init: remove mkdir /dev /proc /sys

* commit '8929c77a':
  init: remove mkdir /dev /proc /sys

These directories are already present in the initial ramdisk, and
these mkdir calls are no-ops.

Change-Id: I528f9e96a3471de904845a2f9e09c1b6ff83a708

* commit 'cd58f488':
  Improve toolbox SIGPIPE behavior.

* commit '6ce5625d':
  Improve toolbox SIGPIPE behavior.