GitLab

Always prepare legacy path, since it's no longer created by init.

Bug: 7255202
Change-Id: I152b44ac62f69923b300abc8d394afe79dac4601

It turns out that some apps swallow the UnsatisfiedLinkError, making it
really hard to work out why they failed to launch.

Before:
  D dalvikvm: Trying to load lib /data/app-lib/com.adobe.air-1/libCore.so 0x415be8a8
  W dalvikvm: No implementation found for native Lcom/adobe/air/AIRWindowSurfaceView;.nativeSurfaceCreated:()V

After:
  D dalvikvm: Trying to load lib /data/app-lib/com.adobe.air-1/libCore.so 0x415be8a8
  E dalvikvm: dlopen("/data/app-lib/com.adobe.air-1/libCore.so") failed: Cannot load library: soinfo_relocate(linker.cpp:975): cannot locate symbol "_ZN7android10VectorImpl19reservedVectorImpl1Ev" referenced by "libCore.so"...
  W dalvikvm: No implementation found for native Lcom/adobe/air/AIRWindowSurfaceView;.nativeSurfaceCreated:()V

Bug: 7093208
Change-Id: Ib751fb959d49cb872d586f299e62ed6aae783de9

This allows the max free to be larger on devices with more memory and
thereby avoid GCs (that may be more frequent due to larger bitmaps).

b/6606849

Change-Id: I4063a303ea4be3c1f227259d699fb238a806451f

Support apps that may manually build OBB paths using
getExternalStorageDirectory() by making multi-user OBB paths live
under user-specific path.

This new structure means we can simplify the emulated_legacy paths
to be a single recursive bind mount.

Bug: 7212801
Change-Id: I85a0caebca52a6ff3bfe61c961518a91f0b8f8ff

* commit '9bd5a9db':
  Fix an ugly bug where try/catch offsets weren't being mapped properly. do not merge.
  Fix a bug where the max blowup of annotations was incorrect. do not merge.
  Fix a bug where debugInfos' size wasn't being computed. do not merge.
  Make dex merging stateless. do not merge.
  Support debug info in dexmerge. do not merge.

Change-Id: If3d2ce0f23b929f92d49649e015386670ed16863

* commit '74d4652e':
  Log when the native trace is unavailable

* commit 'e64cfc1c':
  Log when the native trace is unavailable

* commit 'b79d90eb':
  Log when the native trace is unavailable

This should allow us to differentiate between "couldn't get the
stack" and "didn't try to get the stack".  Also show the thread's
state (e.g. 'R' for running, 'D' for uninterruptible syscall).

Bug 7053953

(cherry-pick of b3667a19.)

Change-Id: I0a40cb3d3cdd9aef8589a39586cccd9c229aa8cb

This should allow us to differentiate between "couldn't get the
stack" and "didn't try to get the stack".  Also show the thread's
state (e.g. 'R' for running, 'D' for uninterruptible syscall).

Bug 7053953

Change-Id: Ibc9e6a6f0fc855a4e5e8e133122232dc939bcb16

am 90f12e0b: am 4535e29e: am a177aa50: Merge "Use 0xde as the poison value after JIT code cache reset."

* commit '90f12e0b':
  Use 0xde as the poison value after JIT code cache reset.

* commit '4535e29e':
  Use 0xde as the poison value after JIT code cache reset.

* commit 'a177aa50':
  Use 0xde as the poison value after JIT code cache reset.

(cherry-pick of 60497bbc.)

Change-Id: I4f8c1bac2ac3bdc1d931e91f3e2e8038fe4c2b5a

Change-Id: Ic25ede5bcd988f240d8c24df6bc5da81e2b03249

am 8e80f76a: am d207be35: am f31a0600: Merge "Optimize those StrictMath routines that are identical to Math routines."

* commit '8e80f76a':
  Optimize those StrictMath routines that are identical to Math routines.

am d207be35: am f31a0600: Merge "Optimize those StrictMath routines that are identical to Math routines."

* commit 'd207be35':
  Optimize those StrictMath routines that are identical to Math routines.

* commit 'f31a0600':
  Optimize those StrictMath routines that are identical to Math routines.

We can just use the existing Math intinsics.

Bug: 7146208
Change-Id: I9e78d33cf65a5dcc5a7c0133e67bd9c3c1e43f23

* commit '91a17e5e':
  Test if new build is kicked off.

Change-Id: I20cffa47e360af1eac86d8a04aa53441f9260bc6

Devices without emulated storage should just skip the tmpfs.

Bug: 7131382
Change-Id: I9c697e4faf7864ec3a2695cd3770fbf0c9a5cce3

Change-Id: Ia6a25f00cb28e80111b78d87180575d57c55b062

When building external storage paths, always include user in path
to enable cross-user paths and aid debugging.

Each Zygote process continues to only have access to the appropriate
user-specific emulated storage through bind mounts. A second set of
mounts continue supporting legacy /sdcard-style paths. For example,
a process running as owner has these mount points:

/storage/emulated_legacy
/storage/emulated_legacy/Android/obb
/storage/emulated/0
/storage/emulated/obb

This change also creates two nested namespaces around zygote. The
first namespace is created when the zygote starts, and it holds a
single writable tmpfs, since rootfs is ro. The second namespace is
created quickly after forking, and is used to hold the private
user-specific bind mounts. (This design saves us from creating a
tmpfs-per-process.)

Bug: 7131382
Change-Id: Id80403ec956f0bff6997411cb1f82f273c76b85f

In dex files, there are several places where one object refers
to another object by its position in the file. The dex merger
is generally very careful to adjust these mappings when combining
dex files.

Unfortunately one of these cases was broken. Each try_item refers
to a corresponding encoded_catch_handler by its byte offset in a
list. Most of the time this byte offset is the same in the input
dex file and the output dex file. But encoded_catch_handlers are
variable-length because they use a variable-length uleb128 encoding
to address the type_idx being caught. When dex files are merged,
some exception types may go from having a small index to having
a large index, increasing the number of bytes required to encode
that index. This breaks our ability to directly copy over offsets
as we were doing previously.

Bug: http://code.google.com/p/android/issues/detail?id=36490

(cherry picked from commit d43341a2)

Change-Id: I4e6ab791925a918513122b46e039c02dfef62ace

I'm not sure where the 1.34 number comes from but it's incorrect.
From the spec, the encoded_annotation is made up of a single byte
plus an unlimited number of uleb128 values. Each of these values
can double in width in the worst case. I received (personal) email
from one user who'd run into a case worse than the incorrect 1.34
limit.

(cherry picked from commit bf7dfeea)

Change-Id: I033a0d76ea0324d434d732e7757df0c3fd925b68

Previously debugInfos' size of 0 caused a malformed dex file
because debug data was present but not mentioned in the table
of contents.

(cherry picked from commit 55ac44b6)

Change-Id: I2084c06521ea200772c523cdaa28c8019fa76025

Using a /storage/sdcard0 symlink and a tmpfs staging area was used
to enable "/sdcard" paths for both zygote processes and the shell
user, but it breaks on devices with both emulated and physical
external storage.

Specifically, vold can't mount a physical sdcard onto the primary
storage symlink, and zygote can't re-bind-mount when secondary
storage is remounted after dropping privileges.

Bug: 7094858, 7064600
Change-Id: Id91e3b3e521a3b3e1bb5358920adc66a0a43917f

* commit 'e599c468':
  Remove unnecessary compiler pragma.

* commit 'cfeacbdd':
  Remove unnecessary compiler pragma.

am 86e036a8: am e6516a53: Merge "Fix an ugly bug where try/catch offsets weren\'t being mapped properly."

* commit '86e036a8':
  Fix an ugly bug where try/catch offsets weren't being mapped properly.