summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-03-25Snap for 9815530 from 8301b33dad51cafd9d08876fc91a7e5fa556dcd3 to ↵android-13.0.0_r83android-13.0.0_r71android-13.0.0_r70android-13.0.0_r69android-13.0.0_r68android-13.0.0_r67android-13.0.0_r63android-13.0.0_r62android-13.0.0_r61android-13.0.0_r56android-13.0.0_r54android-13.0.0_r53android-13.0.0_r52android-13.0.0_r51android-13.0.0_r50android13-qpr3-s9-releaseandroid13-qpr3-s8-releaseandroid13-qpr3-s7-releaseandroid13-qpr3-s6-releaseandroid13-qpr3-s5-releaseandroid13-qpr3-s4-releaseandroid13-qpr3-s3-releaseandroid13-qpr3-s2-releaseandroid13-qpr3-s14-releaseandroid13-qpr3-s1-releaseAndroid Build Coastguard Worker
tm-qpr3-release Change-Id: I326aef6be18c933d13882735331a02317f72b862
2023-03-24Move boringssl self tests from early-init to init.android-13.0.0_r82android-13.0.0_r81android-13.0.0_r80android-13.0.0_r74android-13.0.0_r73android-13.0.0_r72android-13.0.0_r66android-13.0.0_r65android-13.0.0_r64android-13.0.0_r60android-13.0.0_r59android-13.0.0_r58android13-qpr3-c-s8-releaseandroid13-qpr3-c-s7-releaseandroid13-qpr3-c-s6-releaseandroid13-qpr3-c-s5-releaseandroid13-qpr3-c-s4-releaseandroid13-qpr3-c-s3-releaseandroid13-qpr3-c-s2-releaseandroid13-qpr3-c-s12-releaseandroid13-qpr3-c-s11-releaseandroid13-qpr3-c-s10-releaseandroid13-qpr3-c-s1-releasePete Bentley
In previous releases, these self tests had a secondary purpose of writing a flag file to save future processes from running some slow self checks. This is no longer true in T. However running the tests from early-init has caused issues on some devices as the kernel's entropy pool is not yet initialised, causing the process to block for a second or more. Bug: 231946889 Bug: 249037600 Test: m && flashall Change-Id: I2116f2029ca6a21e4359407dfff4dc79edd39084 Merged-In: I2116f2029ca6a21e4359407dfff4dc79edd39084
2023-02-11Snap for 9593491 from 4fb1bf6eecff0948d49c280429c2fa6dd58bdee2 to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I60aee38a74beee9741a5bee560695f6de30708cc
2023-02-10Merge "libsnapshot: Disable 32-bit VTS tests on 64-bit systems." into ↵David Anderson
android13-tests-dev am: cb6ea9edb4 am: 689290a182 am: a91a6a51fb Original change: https://android-review.googlesource.com/c/platform/system/core/+/2427052 Change-Id: I411a7512be6bd8ddd424fd89f9f05ba44972d665 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-02-09Merge "libsnapshot: Disable 32-bit VTS tests on 64-bit systems." into ↵David Anderson
android13-tests-dev am: cb6ea9edb4 am: 689290a182 Original change: https://android-review.googlesource.com/c/platform/system/core/+/2427052 Change-Id: I827180930ee624529c0a45ea864ac76a70e128a0 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-02-09Merge "libsnapshot: Disable 32-bit VTS tests on 64-bit systems." into ↵David Anderson
android13-tests-dev am: cb6ea9edb4 Original change: https://android-review.googlesource.com/c/platform/system/core/+/2427052 Change-Id: Ieacfa1efbef66b0d73da0947dda3f1d5bc6a1c0a Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-02-09Merge "libsnapshot: Disable 32-bit VTS tests on 64-bit systems." into ↵David Anderson
android13-tests-dev
2023-02-09Snap for 9581790 from a4fa9e40fd282fe5f0b18c7b25acadb5b25e8d21 to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I733ae30dbc08ee8896be8166e72dbb48df4cf2de
2023-02-08Merge "Grant wmtrace access to platform_app:systemui" into tm-qpr-devHongwei Wang
2023-02-08libsnapshot: Disable 32-bit VTS tests on 64-bit systems.David Anderson
These tests don't work because 32-bit dependencies are not normally packaged on a 64-bit system. Bug: 263062262 Test: builds Change-Id: I68859a9e9c029a528ee12c02569a3693261c7251 (cherry picked from commit 32fa3e96f4f23256da25fe9115fb3e5011c3299b)
2023-02-03Snap for 9556973 from 719b97add040eb4d60e8a6b87d1e2f35ab73e6a0 to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: Ic660a004b6d2c856b7c446f3f6deb318f0a1808b
2023-02-02Snap for 9552684 from bc680ab1fafffc811896e9723cded4dbde46f39b to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I989d329a5f4de555006e848ad2d4bc1c0536fbf9
2023-02-01Display offset in backtraces if necessary.Christopher Ferris
When moving to a proto tombstone, backtraces no longer contain an offset when a frame is in a shared library from an apk. Add the offset display again if needed, and add a test to verify this behavior. Bug: 267341682 Test: All unit tests pass. Test: Dumped a process running through an apk to verify the offset Test: is present. Change-Id: Ib720ccb5bfcc8531d1e407f3d01817e8a0b9128c (cherry picked from commit 22035ccb01693da3e0ec94776c86988c7d5c617e)
2023-01-31Grant wmtrace access to platform_app:systemuiHongwei Wang
Grant read/write access to anyone for /data/misc/wmtrace folder on debuggable builds, it's further protected by the selinux policy. This is to allow systemui process to write proto logs to the same folder on device as WindowManager, both can contribute to the transitions like PiP, Split-Screen and etc. Bug: 251513116 Test: adb shell dumpsys activity service SystemUIService \ WMShell protolog [start | stop] Ignore-AOSP-First: cherry-pick of aosp/2397772 Merged-In: Ice57efa17c61d132b02c0a11a762c24d772bd90a Change-Id: Ice57efa17c61d132b02c0a11a762c24d772bd90a
2023-01-31Port ADB's new handling of the USB packet ClearFeature(HALT) to Fastboot.Nicolas Gagnon
This patch addresses Fastboot/Fastbootd connection issues seen on ARM Mac devices. Original ADB patch: https://android-review.googlesource.com/c/platform/packages/modules/adb/+/1699250/ Bug: 238779161 Test: 'fastboot update <path_to_update_archive>.zip' now works on ARM Mac. Signed-off-by: Nicolas Gagnon <nicolasgagnon@google.com> Merged-In: Id67904d91abc8b66ef1a00962e1fd57c97df98a7 Change-Id: Id67904d91abc8b66ef1a00962e1fd57c97df98a7 (cherry picked from commit 3efef5694ee242f0fbeeaaa15c128dfb84418798)
2023-01-27Snap for 9531772 from 8ea0c2e276e913ad4d5756e691686573ffad5a03 to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I2f1ce7a503f02106f913282959bc8315103e38cf
2023-01-26Merge "init: Take wakelock on zygote restart" into tm-qpr-devKalesh Singh
2023-01-26Resolve ro.debuggable at build time am: d5e026e1af am: 1de6ea34c3Alessandra Loro
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/21106623 Change-Id: If8523fb54d49472231d69e80b72ad0975c568873 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-01-26Resolve ro.debuggable at build time am: d5e026e1afAlessandra Loro
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/21106623 Change-Id: I7a10a9a5f3397862aba9c2833d71fdf01bad4630 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-01-25init: Take wakelock on zygote restartKalesh Singh
If the framework is restarting (and cannot yet aquire wakelocks to block suspend). Take a kernel wakelock to allow the system to make sufficient progress before autosuspend can be triggered. The wakelock is later disable when the framework has and invokeds enableAutosuspend() on the suspend service. Bug: 255898234 Bug: 265513788 Bug: 266077359 Test: adb shell "echo mem > /sys/power/state && killall system_server" Change-Id: Id8cff6564ef05d8c22a8264c51dd313263cb6a9d Merged-In: Id8cff6564ef05d8c22a8264c51dd313263cb6a9d
2023-01-25Resolve ro.debuggable at build timeAlessandra Loro
Ignore-AOSP-First: cherry-pick for tm-qpr-dev Test: n/a Bug: 193912100 Bug: 243645021 Merged-In: I83b0021b91536335c63d19f8a65933bad1b26b4e Change-Id: I42c4b1e81383d83c73a565c5e74ac22f17389faf
2023-01-17Snap for 9495226 from d7918fad814123e2f6cab6d77bf16826d323de2c to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I2f9c937d3bc172763e15e19ab4bcba294cbe72ea
2023-01-16Snap tm-dev to android13-tests-dev am: fc0ee916bc am: 118a97fb5aSamip Garg
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/20514427 Change-Id: I75805d3c8aa574ef5f88118c68748c7a1f999eb6 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-01-11Snap tm-dev to android13-tests-dev am: fc0ee916bcSamip Garg
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/20514427 Change-Id: Ia96976f302e1bd3d2ffbf2740010e40f4692d12e Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2023-01-11Snap for 9474727 from 8ef2a47c0aae39188d40e6c1936b6dd03776fa7d to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I8f043f9b192fab2b5053c92fe0f477022c37a2e0
2023-01-10Snap for 9470583 from 4762c22aba406edd48e5c3bb91facb74a62a9b6e to ↵Android Build Coastguard Worker
tm-qpr3-release Change-Id: I398badd620b72a27a2b882a8deccdef0c2f68c1c
2023-01-09snapuserd: Update verificationAkilesh Kailash
Initiate update verification from daemon. This will help in two ways: 1: We avoid reading everything into page-cache. Since, low end devices are already short on memory, we don't want to read and populate page-cache which can slow down boot. 2: During boot, once the selinux transition is done, daemon is all ready to kick off the verification since verity is already setup. Note that we are still guarded by update_verifier. Update_verifier will still block marking new slot as boot success until the verification is completed. So, there is no change in the behavior. Bug: 193863442 Bug: 261913544 Test: Full and incremental OTA on Pixel 6 Incremental OTA of 500M (Monthly OTA) Boot-time (Without this patch): 38 seconds Boot-time (With this patch): 32 seconds Full OTA of 2.2G: Boot-time (Without this patch): 27 seconds Boot-time (With this patch): 21 seconds Signed-off-by: Akilesh Kailash <akailash@google.com> Merged-In: I4f17db19bdd0dd261902c670be6212862d861fe1 Change-Id: I4f17db19bdd0dd261902c670be6212862d861fe1
2022-12-08Snap tm-dev to android13-tests-devSamip Garg
Bug:259849956 Merge ab/9299233 Merged-In: I1795c931b28fd5fe28aa0f23717d4238fb352d37 Change-Id: I1fbab8fc336954dddd623a4a5724fa0e724b4f62
2022-11-30trusty/storage: Add property indicating when fs is readyStephen Crane
Adds a system vendor property (ro.vendor.trusty.storage.fs_ready) to indicate when backing storage on the Android filesystem (e.g. /data) is ready for use. Before this property is set, the Trusty storage proxy may restart causing connections in Trusty to the storage service to be disconnected. All Trusty operations that may require storage and can wait until the device filesystems are ready should wait on this property. Bug: 258018785 Test: manual Change-Id: I9b1408b72df34a0d0cbcc1b99e9617f15bc47558 Ignore-AOSP-First: Topic did not auto-merge from AOSP
2022-11-21Merge "Resolve ro.debuggable at build time" into tm-qpr-devAlessandra Loro
2022-11-15Merge "Create misc_ce and misc_de mirror storage" into tm-qpr-devSanjana Sunil
2022-11-01Resolve ro.debuggable at build timeAlessandra Loro
Ignore-AOSP-First: cherry-pick for tm-qpr-dev Test: n/a Bug: 193912100 Bug: 243645021 Merged-In: I83b0021b91536335c63d19f8a65933bad1b26b4e Change-Id: I42c4b1e81383d83c73a565c5e74ac22f17389faf
2022-10-11init: Support reboot reason with thermal warmresetSayanna Chandula
Thermal shutdown could be due to tskin temperature or battery temperature. Pass reason while rebooting the system to reflect properly in boot.reason Bug: 238464124 Test: Build and boot on device. Check reboot reason for thermal shutdown and battery thermal shutdown with thermal warmreset enabled. Ignore-AOSP-First: AOSP already contains the change Change-Id: I192562fed48ae7da7843e383362cd22a76ce479f Merged-In: I192562fed48ae7da7843e383362cd22a76ce479f
2022-10-05Add AID for PRNG seeder daemon.Pete Bentley
Also adjust permissions on /dev/hw_random to allow prng_seeder group read access. Manual testing protocol: * Verify prng_seeder daemon is running and has the correct label and uid/gid. * Verify prng_seeder socket present and has correct label and permissions * Verify no SELinux denials * strace a libcrypto process and verify it reads seeding data from prng_seeder (e.g. strace bssl rand -hex 1024) * strace seeder daemon to observe incoming connections (e.g. strace -f -p `pgrep prng_seeder`) * Kill daemon, observe that init restarts it * strace again and observe clients now seed from new instance Bug: 243933553 Test: Manual - see above Change-Id: I4d526844b232fc2a1fa5ffd701ca5bc5c09e7e96 Merged-In: I4d526844b232fc2a1fa5ffd701ca5bc5c09e7e96 (cherry picked from commit 6cb61610e619e31bd22c12895ec0ca623f793127)
2022-10-04Merge "init: Add option to listen on sockets before starting service." into ↵Pete Bentley
tm-qpr-dev
2022-09-30charger: fix secondary display not turning off after first display was offJack Wu
turn off both display after first display was turned off Bug: 242967285 Test: charging animation can show in display correctly Ignore-AOSP-First: cherry-pick from aosp Signed-off-by: Jack Wu <wjack@google.com> Change-Id: Ie5741b49322aaf8a3750b1977fb203e4d0df3539
2022-09-22init: Add option to listen on sockets before starting service.Adam Langley
Review note: Original change was a p-o-c by agl in https://r.android.com/2094350 which I think is actually production quality. I'm just taking it over so that he doesn't get spammed by any review comments as that's not a good use of his time. Needed for the hardware entropy daemon (see bug). Original commit message: If one needs to create a service that synchronously starts listening on a socket then there are currently no good options. The traditional UNIX solution is to have the service create the socket and then daemonise. In this situation, init could start the service with `exec_start` and yet not block forever because the service forks and exits. However, when the initial child process exits, init kills the daemon process: > init: Killed 1 additional processes from a oneshot process group for > service 'foo'. This is new behavior, previously child processes > would not be killed in this case. Next, there is a `socket` option for services and (although the documentation didn't nail this down), the socket is created synchronously by `start`. However, init doesn't call `listen` on the socket so, until the service starts listening on the socket itself, clients will get ECONNREFUSED. This this change adds a `+listen` option, similar to `+passcred` which allows a socket service to reliably handle connections. Bug: 243933553 Test: Started prng_seeder from init using the new listen flag Change-Id: I91b3b2b1fd38cc3d96e19e92b76c8e95788191d5 Merged-In: I91b3b2b1fd38cc3d96e19e92b76c8e95788191d5 (cherry picked from commit ecc14a595809846cd09760d2c59b1fdfa9660ce8)
2022-09-21Merge "Some device that platform base on android12 doesn't support A/B ↵Treehugger Robot
update, it looks virtual A/B is also not mandatory. so this test case should check ro.vendor.api_level first." into android13-tests-dev
2022-09-17Some device that platform base on android12 doesn't support A/B update, it ↵biandonglei
looks virtual A/B is also not mandatory. so this test case should check ro.vendor.api_level first. test: run vts -m vts_ota_config_test -t VAB#Enabled issue: 245441425 Change-Id: I1795c931b28fd5fe28aa0f23717d4238fb352d37
2022-09-15Create misc_ce and misc_de mirror storageSanjana Sunil
Create a mirror directory for misc_ce and misc_de storage by bind mounting the respective directories. This is done for the defaul null volume only, and other volumes are handled at a later staged. When an SDK sandbox process is spawned and data isolation needs to occur, the sdksandbox directories present in the misc directories will be used to bind mount from, after tmpfs is mounted on the original. Bug: 214241165 Test: atest GtsSdkSandboxInprocessTests Ignore-AOSP-First: Will cherry pick based on other CLs in the topic Change-Id: Icb1dc7d7fbd53a5c3853acf2f9d4d75b278d7295 Merged-In: Icb1dc7d7fbd53a5c3853acf2f9d4d75b278d7295
2022-09-07trusty/apploader: Handle APPLOADER_ERR_NOT_ENCRYPTEDPer Larsen
Add a specific error message to the Android CLI tool for the case where the apploader rejected an attempt to load an application which requested encryption of its ELF image via its manifest while containing an unencrypted ELF image. Bug: 241824652 Change-Id: Ib2a3c881015700492b8166be38c41753bf51b3b2 (cherry picked from commit db9a554a2f30c1592f8825303a4d5131d6b32a2e) Merged-In: Ib2a3c881015700492b8166be38c41753bf51b3b2
2022-09-07trusty/apploader: Add missing doc for enum valuePer Larsen
Document the APPLOADER_ERR_POLICY_VIOLATION value in enum apploader_error. Bug: 208968719 Change-Id: Ia9b17f4ea705d13567b2ba74f2dcd6df5a0c7d73 (cherry picked from commit c5253819f85486ee40ae13f59742afeba8f8ef58) Merged-In: Ia9b17f4ea705d13567b2ba74f2dcd6df5a0c7d73
2022-08-31Prepare /data/property before load_persist_propsJooyung Han
Without the directory (this happens on the very first boot), load_persist_props can't create an initial version of /data/property/persistent_properties (probably empty). This leads to persisting all in-memory "persist.*" properties later when a persistent property is set. This is regression from Android S because persistent props from, for example, build.prop will be persisted even when there's no process to explicitly setprop. Bug: 242264580 Bug: 243958304 Test: launch cuttlefish and verify that there's no props from build.prop Merged-In: I5819a97750e4d5d1ee5a7c308bf944c7aeab2f90 Change-Id: I5819a97750e4d5d1ee5a7c308bf944c7aeab2f90 (cherry picked from commit 95614963039be8500c6f2a81194e97e01b35bc7b)
2022-08-29Merge "libsnapshot: Remove flaky image creation test." into android13-tests-devDavid Anderson
2022-08-18libsnapshot: Remove flaky image creation test.David Anderson
This test has always been flaky, and is not testing something super valuable: we know that image creation succeeds throughout the rest of the suite, so it's not very interesting to know that it can succeed in a low-space scenario. The inverse test is much more valuable, since we want the correct status code when creation fails due to low space. Bug: 240391002 Test: vts_libsnapshot_test Change-Id: I6235d11033d2f30efe530077b877863ba2574810 (cherry picked from commit 97e8a2f0e963cea957ffd135be4436de3b3afd6a)
2022-08-12libsnapshot: Store index of COW ops vectorAkilesh Kailash
Using vector + unordered_map to retrieve the index in a COW op vector consumes significant memory; this is a problem especially when there are hundreds of thousands of operations. Instead, just store the index of the COW op vector during pre-processing. On Pixel, peak memory usage when all the partitions are mapped: Without patch: RssAnon: 118804 kB With path: RssAnon: 55772 kB Additionally, post OTA reboot, memory usage further goes down as the partition merge completes. Bug: 237490659 Test: OTA on Pixel Ignore-AOSP-First: cherry-pick from aosp Signed-off-by: Akilesh Kailash <akailash@google.com> Change-Id: Icc68a9688ceb89572821cee2dac689779f5e7c11
2022-08-04storageproxy: Report fsync failures with a distinct error code am: cf458bae1eStephen Crane
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/19517837 Change-Id: I0cec6b12306b037503160b56ceecdb95acc4bde3 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2022-08-04storageproxy: Support POST_COMMIT sync for all commands am: 5b02ed521cStephen Crane
Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/19517836 Change-Id: I3aeeb035f1168bd2c9bdbba43ddd014c92d8a8c9 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2022-08-03storageproxy: Report fsync failures with a distinct error codeStephen Crane
Fsync failures are special because they may indicate a failure of an operation before the current operation. Report these cases as a new, distinct error. Test: Cause fsync failure and check error response Bug: 239105007 Change-Id: Ie9d4a1949586e90006256c975786e21ced655e66 Merged-In: Ie9d4a1949586e90006256c975786e21ced655e66 (cherry picked from commit 1c75d1e3a7a70881879ab751747eeba39da98d7b)
2022-08-03storageproxy: Support POST_COMMIT sync for all commandsStephen Crane
Previously we did not support STORAGE_MSG_FLAG_POST_COMMIT for anything but RPMB operations (in which case it was a no-op). We need to support this flag in order to store a superblock in non-secure storage, as we need that write to commit atomically wrt all other writes. Test: com.android.storage-unittest.nsp Bug: 228793975 Change-Id: Ia453c1916970e0b65a91e42f18b920ac4e1f01db Merged-In: Ia453c1916970e0b65a91e42f18b920ac4e1f01db (cherry picked from commit 57770a531885cea930f8c56a311c0a0c530abdad)
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 07:17:52 +0000