Commit Graph

41121 Commits

Author SHA1 Message Date
Mark Salyzyn 75046897b3 bootstat: add reboot,rescueparty
Reserve this for Android system use.

Test: none
Change-Id: Iaf29f0fcd1fe68962cf1109843d6452d0ab42e3c
2018-05-03 13:13:34 -07:00
android-build-prod (mdb) e415282cec Merge "Update shell and utilities docs." am: fcfbaa2ad6
am: 54cfee18a3

Change-Id: I65b9c5bba256ff0a26a9d35b67f6e3df38b74b87
2018-05-03 13:01:03 -07:00
android-build-prod (mdb) 54cfee18a3 Merge "Update shell and utilities docs."
am: fcfbaa2ad6

Change-Id: Ie716910d9d43e665c6c10a4da08ec5ed1959275b
2018-05-03 12:54:55 -07:00
android-build-prod (mdb) fcfbaa2ad6 Merge "Update shell and utilities docs." 2018-05-03 19:44:18 +00:00
Yifan Hong a922d6b596 healthd: Add elsk as OWNERS
Test: none
Change-Id: I676621ced38308296c32259c9525a8d55948e937
2018-05-03 12:25:00 -07:00
Elliott Hughes 4c4b30d7b7 Update shell and utilities docs.
For both P and Q.

Bug: N/A
Test: N/A
Change-Id: I85572bd71871a30c5e6761e098c0d4c63563e873
2018-05-03 11:02:07 -07:00
Elliott Hughes 03d183aecc Tell the build system about APCT's requirements.
Bug: N/A
Test: N/A
Change-Id: I8a67e1ce5acc4142387878ba0bb542da0861e700
2018-05-03 10:06:45 -07:00
David Anderson 5a4db628ee fs_mgr: clean up dm ioctl flags
DM_READONLY_FLAG should only be used when loading tables, and
DM_STATUS_TABLE_FLAG should only be used when querying a table's status. This
patch cleans up how we set flags to reflect when the kernel actually cares
about them.

Bug: 78914864
Test: AVB device still boots

Change-Id: I809d8c2ef2105849ebdd095bbe7f08f15ae63465
2018-05-02 18:46:20 -07:00
android-build-prod (mdb) c86ba29c71 Merge "Compile toolbox's newfs_msdos for the host" am: fb8b76fe55
am: 1f6980b42b

Change-Id: Ie36dff2bb4e2c28b496947388ecd79cce557b182
2018-05-02 15:10:43 -07:00
android-build-prod (mdb) 1f6980b42b Merge "Compile toolbox's newfs_msdos for the host"
am: fb8b76fe55

Change-Id: Ia69e2697fc597dbb2f76cabd71877baf215b9baf
2018-05-02 15:07:09 -07:00
android-build-prod (mdb) 387241329d Merge "tombstoned: don't create tombstones for failed dumps." am: 294d41cb83
am: d40a081623

Change-Id: I1a85540ce536a594882a12cef03027f9e48e71fa
2018-05-02 14:57:19 -07:00
android-build-prod (mdb) 7d5a32e572 Merge "Fix a debuggerd test expectation." am: dbc4aa1ded
am: d724371524

Change-Id: I8eb792a4c7be9aba16314c033132cc06ab5ca52c
2018-05-02 14:56:10 -07:00
android-build-prod (mdb) fb8b76fe55 Merge "Compile toolbox's newfs_msdos for the host" 2018-05-02 21:55:04 +00:00
android-build-prod (mdb) d40a081623 Merge "tombstoned: don't create tombstones for failed dumps."
am: 294d41cb83

Change-Id: Ia94317bd46773d6199853ded19ea804abbaf68c9
2018-05-02 14:50:46 -07:00
android-build-prod (mdb) d724371524 Merge "Fix a debuggerd test expectation."
am: dbc4aa1ded

Change-Id: Ic415ee262efa603fadfee7e2e95ef7ed36d6f966
2018-05-02 14:50:17 -07:00
Josh Gao 598061ff6d tombstoned: don't create tombstones for failed dumps.
Instead of creating tombstone FDs in place and passing them out to
crash_dump directly, create them as O_TMPFILEs and link them into place
when crash_dump reports success, to avoid creating empty tombstones
in cases like an aborting thread racing with another thread that
manages to cleanly exit_group before the dump finishes.

Bug: http://b/77729983
Test: debuggerd_test
Test: adb shell 'for x in `seq 0 50`; do crasher; done'
Change-Id: I31ce4fd4a524abf8bde57152450209483d9d0ba9
(cherry picked from commit 48383c806a)
2018-05-02 14:43:50 -07:00
android-build-prod (mdb) 294d41cb83 Merge "tombstoned: don't create tombstones for failed dumps." 2018-05-02 21:43:03 +00:00
android-build-prod (mdb) dbc4aa1ded Merge "Fix a debuggerd test expectation." 2018-05-02 21:41:43 +00:00
Dan Willemsen a228822c7d Compile toolbox's newfs_msdos for the host
For potential use with build/make/tools/fat16copy.py

Bug: 63035155
Test: mmma system/core/toolbox; newfs_msdos
Change-Id: I8ad50b8c181fc4ec21e191ec9fea8e9aa11d2d9b
2018-05-02 13:14:51 -07:00
David Anderson 29954f6062 init: refactor first stage to not require fstab
In order to support dm-linear devices, we need an additional first-stage
step to ensure that required devices are created. This must happen before
setting up dm-verity or mounting any first-stage partitions.

This patch refactors FirstStageMount so that having a compatible fstab
is optional. This will let us use InitRequiredDevices on systems that
would not otherwise perform first-stage mounts.

Bug: 78914864
Test: non-AVB devices still boot
Change-Id: I11265375a9900d983da8cabcc77d32c503ded02e
2018-05-02 12:23:15 -07:00
Elliott Hughes 89722709b4 Fix a debuggerd test expectation.
70d8f28945 broke a test that was not
expecting to see the new detail about the signal's sender.

Bug: http://b/78594105
Test: ran tests
Change-Id: Idfa3a53b9e664308efdba560ffbb1401c1904530
2018-05-02 10:49:13 -07:00
Mathew Inwood 348ec23d1e Merge "Add support for logging package name." into pi-dev
am: 979931803b

Change-Id: I9c39633e271afa1979cd3fc7e627022e92d11fac
2018-05-02 03:46:33 -07:00
Mathew Inwood 979931803b Merge "Add support for logging package name." into pi-dev 2018-05-02 10:39:15 +00:00
Bowgo Tsai 02701a27de [automerger skipped] First-stage mount: avoid triggering a FATAL error
am: fe92dd0973  -s ours

Change-Id: I483b2b885de4c9310e509a591133269a14f4d619
2018-05-01 21:34:08 -07:00
Bowgo Tsai 0537233531 Merge "First-stage mount: avoid triggering a FATAL error" am: 78393951de
am: d8829d7a4f

Change-Id: I4f8c500e04245bf9be3913be5710d47f635b53e0
2018-05-01 19:35:34 -07:00
Bowgo Tsai d8829d7a4f Merge "First-stage mount: avoid triggering a FATAL error"
am: 78393951de

Change-Id: Idac1a2c9b922308ec8861c15979e29184dde5bdb
2018-05-01 19:31:30 -07:00
Bowgo Tsai fe92dd0973 First-stage mount: avoid triggering a FATAL error
Related AOSP changes:
  1. https://android-review.googlesource.com/#/c/platform/system/core/+/405009/
  2. https://android-review.googlesource.com/#/c/platform/system/core/+/532637/

The second CL raises a FATAL error when it detects fstab-dt has no content
during first-stage mount. However, with the first CL, the fstab-dt entry
might be "skipped" when bootloader sets the status property to a value
other than "ok"/"okay". (e.g., to skip mounting /vendor on upgrading
devices which have no vendor partition).

Use LOG(INFO) when there is nothing to mount here. The later stages
should trigger a FATAL error when some important files in those
partitions are not available, e.g., SEPolicy files.

Bug: 78441220
Test: boot a device
Change-Id: Iae2f47d455679298bdb067d96b771a30c1a82e6f
Merged-In: Iae2f47d455679298bdb067d96b771a30c1a82e6f
(cherry picked from commit 8fe363f260)
2018-05-02 10:23:16 +08:00
Bowgo Tsai 78393951de Merge "First-stage mount: avoid triggering a FATAL error" 2018-05-02 02:16:58 +00:00
android-build-prod (mdb) 4f3fd04cd1 Merge "adb: Avoid waiting for emulator connections" am: 8ef8d1eb6b
am: 142eeae546

Change-Id: I4d9a888b7d7521ad0428aa33af6d24143818162b
2018-05-01 19:00:15 -07:00
android-build-prod (mdb) 142eeae546 Merge "adb: Avoid waiting for emulator connections"
am: 8ef8d1eb6b

Change-Id: I3720cad78b1d8449c3e1cfedc57bc3c673c73b80
2018-05-01 18:55:31 -07:00
android-build-prod (mdb) 8ef8d1eb6b Merge "adb: Avoid waiting for emulator connections" 2018-05-02 01:46:12 +00:00
Josh Gao 83d7ef4a7c Merge changes from topic "unwindstack_clone" into pi-dev
am: 3bac1ffdd0

Change-Id: I1808e87e15e7e9eae3a9f13217f5376bb3f69f5a
2018-05-01 17:17:08 -07:00
Luis Hector Chavez c587f02cc6 adb: Avoid waiting for emulator connections
This change exempts the emulator connections from
WaitableConnection.WaitForConnection(). This is because emulator
connections are a) more reliable and b) handled a bit differently than
normal TCP connections.

Bug: 78991667
Test: emulator -showkernel ; adb shell
Change-Id: I552946198889a82d6c265f45e8c3b38f6ac9d045
2018-05-01 17:12:16 -07:00
Josh Gao 3bac1ffdd0 Merge changes from topic "unwindstack_clone" into pi-dev
* changes:
  libdebuggerd: clone registers before we Unwind with them.
  libunwindstack: add Regs::Clone.
2018-05-02 00:03:50 +00:00
Josh Gao 6796735e2a crash_dump: defuse our signal handlers earlier.
am: f7023c9844

Change-Id: Ic2733269d84418b7078bc16dc90286abdfca0c5f
2018-05-01 14:27:18 -07:00
Mathew Inwood 9079f7c283 Add support for logging package name.
The functionality already exists in Java, add it to the C++ class too.

Bug: 77517571
Test: m
Test: Exercised by ag/3984344 in art
Change-Id: Id27a6c506783a02e4334498dadf55167efab097f
2018-05-01 16:21:44 +01:00
Bowgo Tsai 8fe363f260 First-stage mount: avoid triggering a FATAL error
Related AOSP changes:
  1. https://android-review.googlesource.com/#/c/platform/system/core/+/405009/
  2. https://android-review.googlesource.com/#/c/platform/system/core/+/532637/

The second CL raises a FATAL error when it detects fstab-dt has no content
during first-stage mount. However, with the first CL, the fstab-dt entry
might be "skipped" when bootloader sets the status property to a value
other than "ok"/"okay". (e.g., to skip mounting /vendor on upgrading
devices which have no vendor partition).

Use LOG(INFO) when there is nothing to mount here. The later stages
should trigger a FATAL error when some important files in those
partitions are not available, e.g., SEPolicy files.

Bug: 78441220
Test: boot a device
Change-Id: Iae2f47d455679298bdb067d96b771a30c1a82e6f
2018-05-01 16:39:36 +08:00
Tao Bao d5a261670c Merge changes from topic "libsparse-callback" am: 49b7f296b9
am: b2cacbb983

Change-Id: If7807fcc8b33f9a404c25ea53917462b3a320a32
2018-04-30 16:18:51 -07:00
Tao Bao 4f46ef48cf libsparse: Use 'size_t' for the 'len' parameter in callbacks. am: e18c03165b
am: 315efbeb9a

Change-Id: I2cf89d54f1c266a5cfd6107e49378cb3d344ef4b
2018-04-30 16:18:26 -07:00
Tao Bao b2cacbb983 Merge changes from topic "libsparse-callback"
am: 49b7f296b9

Change-Id: I106758e1ba319e0b2f1a912fe383f5ab5752ee2f
2018-04-30 16:02:15 -07:00
Tao Bao 315efbeb9a libsparse: Use 'size_t' for the 'len' parameter in callbacks.
am: e18c03165b

Change-Id: I8ac1fc964bf8245dcc274c57656eb12425693b77
2018-04-30 16:01:43 -07:00
Josh Gao f7023c9844 crash_dump: defuse our signal handlers earlier.
We have a LOG(FATAL) that can potentially happen before we turn off
SIGABRT. Move the signal handler defusing to the very start of main.

Bug: http://b/77920633
Test: treehugger
Change-Id: I7a2f2a0f2bed16e54467388044eca254102aa6a0
(cherry picked from commit 38ac45df17)
2018-04-30 14:52:12 -07:00
Tao Bao 49b7f296b9 Merge changes from topic "libsparse-callback"
* changes:
  fastboot: Track the libsparse API change.
  libsparse: Use 'size_t' for the 'len' parameter in callbacks.
2018-04-30 21:48:46 +00:00
Elliott Hughes da6a06548a Merge "Add test_suites lines." am: 4e6f3d9603
am: d16019bd7d

Change-Id: Ie9535898e31c62e1baa9c70a7257ab39fcddc93e
2018-04-28 09:14:34 -07:00
Elliott Hughes d16019bd7d Merge "Add test_suites lines."
am: 4e6f3d9603

Change-Id: I5e12282fcd3e5d609f5ef5c47a9218e18d2ecda2
2018-04-28 09:09:54 -07:00
Elliott Hughes 4e6f3d9603 Merge "Add test_suites lines." 2018-04-28 16:02:40 +00:00
android-build-prod (mdb) 034defb01d Merge "crash_dump: defuse our signal handlers earlier." am: c314d4db9f
am: e315b34fd8

Change-Id: If380df4e0ba324737137a41dbc9b0f308abc8024
2018-04-27 16:42:07 -07:00
android-build-prod (mdb) e315b34fd8 Merge "crash_dump: defuse our signal handlers earlier."
am: c314d4db9f

Change-Id: I84666ea2b3239e013a02891fe3ca89e44966f151
2018-04-27 16:36:41 -07:00
android-build-prod (mdb) bfb3b3b217 Merge "adb: Make the Connection object a std::shared_ptr" am: 2666955d3d
am: 3a4c6abb2e

Change-Id: Ie04cabb62bb3489fbcc1573c0440b289515e1961
2018-04-27 16:32:31 -07:00
android-build-prod (mdb) c314d4db9f Merge "crash_dump: defuse our signal handlers earlier." 2018-04-27 23:29:00 +00:00