system_core, branch replicant-9

init: Create /dev/xmm6262_boot0 for i9300

2020-02-10T18:19:53+00:00

For some reason the shell script and its associated service that
are supposed to do that don't end up creating /dev/xmm6262_boot0.

As init does create dev nodes, it's safer to assume that it's
supposed to work.

For devices not needing /dev/xmm6262_boot0, having an
unused dev node should probably not create any issue.

Signed-off-by: Denis 'GNUtoo' Carikli

HACK: gatekeeperd: force software imeplementation

2019-07-14T14:59:36+00:00

Without that hack, IGatekeeper::getService() will try to get
a service implementing the Gatekeeper HAL. The HAL is supposed
to talk to a component that resides in a Trusted Execution
Environment (TEE) such as MobiCore.

On many Android device, the Trusted Execution Environment
is not free software, nor under the control of the user, so it
cannot be trusted by the user, and in fact it's better, if possible,
to make sure that it does not to run at all in that case.

Because of that the proper fix would be either to implement
a Gatekeeper HAL that would not depend on nonfree software that
cannot be trusted.

This could for instance be implemented by:
* Using a simple software implementation.
* Using the linux kernel keyring for that which can
  provide good resilience against userspace trying to get key
  material. See man 7 keyrings for more information on that.
* Have a free software Trusted Execution Environment like
  Google's Trusty or other implementations.

See the following documentation for more background information:
https://source.android.com/security/authentication/gatekeeper

Signed-off-by: Denis 'GNUtoo' Carikli

Use more relaxed VNDK config

2019-07-14T14:59:36+00:00

This allows graphics libraries to communicate with each other.

Change-Id: I4c66e86b6353a174584ff77b38989713f2f77a9e
Signed-off-by: Joonas Kylmälä

Merge remote-tracking branch 'aosp/pie-gsi' into lineage-16.0-pie-gsi

2019-07-13T16:59:47+00:00

* aosp/pie-gsi:
  tombstoned: fixed tombstones failed issue
  health: Add CAP_WAKE_ALARM to service via init
  Add native vsock support to ADB.
  Fix two clang-tidy issues in crasher.cpp.
  fs_mgr_fstab: Add Adiantum support
  fs_mgr_fstab: Add Adiantum support

Change-Id: I12e1150c4e222a945d57614c7c9b82cae91b7643

fastboot: Add --cmdline alias

2019-07-12T16:01:11+00:00

* Current master moved to --cmdline
* Some scripts /mine/ uses --cmdline

Change-Id: I7db75240d0ad4d74036515216bb0560abd871343

Merge tag 'android-9.0.0_r44' into staging/lineage-16.0_merge-android-9.0.0_r44

2019-07-01T23:16:14+00:00

Android 9.0.0 Release 44 (PQ3A.190705.003)

* tag 'android-9.0.0_r44':
  DO NOT MERGE Start update_verifier early in late-fs.

Change-Id: Ie9ca03dbf5dde218f548ba9b7ef0fd1022622358

Merge "tombstoned: fixed tombstones failed issue" into pie-gsi

2019-06-13T16:34:35+00:00

fs_mgr: Add MF_WRAPPEDKEY flag

2019-06-08T19:41:51+00:00

Use separate flag to check wrapped key
support for FBE rather than file contents
mode.

CRs-Fixed: 2316112
Change-Id: Ied59d43a82b6fe9157fd2db405de28549e98982c

fs_mgr: Wrapped key support for FBE

2019-06-08T13:42:07+00:00

Add "ice_wrapped_key_supported" support to be read from
fstab.

CRs-Fixed: 2288316

Change-Id: I01f634e8d464059791d731d2af690bdfd8008107

tombstoned: fixed tombstones failed issue

2019-06-07T19:32:43+00:00

There is a problem about tombstone, which it will fail to
generate tombstone file in some scenarios due to socket
communication exception.

Reproduce step:
step 1: reboot device
step 2: ps -ef |grep zygote , get the pid of zygote64
(Attention: zygote64 should never been killed or reboot,
otherwise we can get the tombstone file)
step 3: kill -5 pid of zygote64
step 4: cd data/tombstones/, and could not find the tombstone
file of zygote64.

[Cause Analysis]
1. There are following logs by logcat:
11-19 15:38:43.789   569   569 F libc : Fatal signal 5 (SIGTRAP),
code 0 (SI_USER) in tid 569 (main), pid 569 (main)
11-19 15:38:43.829  6115  6115 I crash_dump64: obtaining output
fd from tombstoned, type: kDebuggerdTombstone
11-19 15:38:43.830   569  5836 I Zygote  : Process 6114 exited
cleanly (0)
11-19 15:38:43.830   777   777 I /system/bin/tombstoned: received
crash request for pid 569
11-19 15:38:43.831  6115  6115 I crash_dump64: performing dump of
process 569 (target tid = 569)
...
11-19 15:38:43.937   777   777 W /system/bin/tombstoned: crash
socket received short read of length 0 (expected 12)
2. The last log was print by function of crash_request_cb in
file of tombstoned.cpp, following related code:
  rc = TEMP_FAILURE_RETRY(read(sockfd, &request, sizeof(request)));
  if (rc == -1) {
    PLOG(WARNING) << "failed to read from crash socket";
    goto fail;
  } else if (rc != sizeof(request)) {
    LOG(WARNING) << "crash socket received short read of length " << rc << " (expected "
                 << sizeof(request) << ")";
    goto fail;
  }

Tombstoned read message by socket, and now the message length is
zero. Some socket communication exception occurs at that time.
We try to let crash_dump resend the socket message when the
communication is abnormal. Just as this CL.

Test: 1 reboot device
      2 ps -ef |grep zygote , get the pid of zygote64
       (Attention: zygote64 should never been killed or reboot,
       otherwise we can get the tombstone file)
      3 kill -5 pid of zygote64
      4 cd data/tombstones/, and could find the tombstone file of
       zygote64.

Change-Id: Ic152b081024d6c12f757927079fd221b63445b18
(cherry picked from commit 8ac2f27cc2fa5fbfc1bbd1cede906d254a77f862)