Fix a few bugs in rand_emmc_perf

Fix the code to properly read urandom to init the random number generator.
Fix to properly read the arguments if any options are given.
Fix to enable it to be built against glibc.

Change-Id: I9127a71232e39afa3054fe9f1612def9ae13d9d3
Store the uid and gid (when running on an Android device). Create a utility executable.

Change-Id: Iae0560ceaf1663a8ac123ef09e213fa2798a7178
mkimage for OMAP
remove su for Superuser version.
ext4_utils: add BoardConfig define to suppress EMMC-corrupting wipe command

If BOARD_SUPPRESS_EMMC_WIPE is true, the EMMC wipe command will not be
issued. This works around a bug in some firmware revisions of Samsung EMMC's
that permanently damages the device when the wipe command is issued.

For affected devices with kernel source, MMC_CAP_ERASE should be removed
from the kernel instead.

This is only part of the solution but it does handle the "flashing CM9
for the first time on an unsafe kernel" situation.

Change-Id: Ie4e31f9268a65218e5d344ae3068b021790fc33c
Store the uid and gid (when running on an Android device). Create a utility executable.

Change-Id: Iae0560ceaf1663a8ac123ef09e213fa2798a7178
ext4: Let make_ext4fs be grandfathered into builds

the asec containers switched from vfat to ext4 in JB, so
make_ext4fs isn't really optional anymore

Change-Id: I2b5820eaa1eda223e52fa33ea9a6744fe0361b65
ext4_utils: Fix bad merge of EMMC wipe suppression

The order of the modules in the Makefile changed.

The Makefile items for eMMC wipe suppression should be
in the sections for target static and dynamic
libext4_utils.  These were the first two modules in the
file previously, but no longer are.

Move the eMMC wipe configuration handling to the proper
modules.

Change-Id: I86861a89824af04a3b08e75049580df28bd239f7
Merge branch 'jb-release' of https://android.googlesource.com/platform/system/extras into aosp
procrank/procmem fail on 0-length page mappings

procrank prints messages such as:
warning: could not read usage for 279
and does not include that pid in its table of results

procmem segfaults when run against that process

The problem is the 0-length page map at the top of the stack:

beb39000-beb39000 rw-p 00000000 00:00 0
beb39000-beb5a000 rw-p 00000000 00:00 0          [stack]

This patch changes the code to skip over that 0-length mapping when calculating
memory usage

Change-Id: I02aaaecdf64affbd28ab43a2d0865edda33816bc
Merge branch 'jb-mr1-release' of https://android.googlesource.com/platform/system/extras into mr1

Change-Id: Idd8ad3d072643c7c818e332af1c62a4f1885cafe
make_ext4fs: fix static utility executable

- static version of libext4_utils is now
  libext4_utils_static
- add libsparse_static to LOCAL_STATIC_LIBRARIES

Change-Id: I2d2e4eafe69f46d848d5b39b4e11ba163b7d25e5
Merge commit 'android-4.2.1_r1.2' into cm-10.1

Change-Id: I6092a813f02583d25ffe39db8f9e95e458eef5ef
Merge tag 'android-4.2.2_r1' of https://android.googlesource.com/platform/system/extras into 1.1

Android 4.2.2 release 1
make_ext4fs: fix static utility executable, this time for SELinux

Change-Id: Idb924d05a4878765793dd9b5fbd53a3dcbd3c536
tests: Use -fno-strict-aliasing for memtest

There's just no way to do this piece correctly:
    int dummy = 0;
    printf("corrupting our stack...\n");
    *(volatile long long*)&dummy = 0;

Change-Id: If02ff71b3c23c3d8118694f6edba0ecf904baf8a
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
build bionic libc tests as part of system image

Change-Id: Ie8cdd07d2b82c37446a58d1ddaedceef45d7f407
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
update how we run test_system test

Change-Id: I25e6251f83dd90610f67408d1c9522b16fa380dd
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
Merge tag 'android-4.3_r2.1' into cm-10.2

Android 4.3 release 2.1

Conflicts:
	ext4_utils/Android.mk
	ext4_utils/make_ext4fs.c
	su/su.c

Change-Id: I746791f25ab5700195f87dab33160cfee408a6d0
ext4_utils: fix utility build (SELinux)

Change-Id: Idc3b98af7f4138532a91a3d19ec21eae1d4b8698