Age | Commit message (Collapse) | Author |
|
"LA.QSSI.13.0.r1-09800-qssi.0"
Change-Id: Ib4084f349a37cfbf4c089d375b6b1a3a455bbda7
|
|
Change-Id: I2a256e2cde22db9314a5deb2cf89ec7817102b8e
|
|
t-keystone-qcom-release
Change-Id: Iacc4ce0f84236b93cc26cc0d47476d26a5011ce7
|
|
Change-Id: I6990163e04c81cd29f66e6b23ccbcf446bbcf179
|
|
tm-platform-release
Change-Id: Id29fb2f600d9c167e401dd119056564b8f6ed01f
|
|
Bug: 269346300
Change-Id: Ieea7d214f7bc6fd61036f207ea5691b4b85ed36e
|
|
Change-Id: I4601ec0508e353c4c0153936858f43aa4761e30f
|
|
t-keystone-qcom-release
Change-Id: Ib00ca89a45a2cebf7c9c39efd3d72bca17478d9b
|
|
Change-Id: Id1317e38eda87b2b519afbed7b1e22323640c271
|
|
tm-platform-release
Change-Id: Id6258cef9aeb42564a4787ad09fa68c6e7b13a94
|
|
sso://googleplex-android/platform/bionic into HEAD
Change-Id: I10cb98c0ac8421ed8fed8c1e0c0e6c3b93b77350
|
|
tm-qpr2-release
Change-Id: I3241535aca435bfcb28242f423d28d37bb0c5a18
|
|
Overall, jemalloc performs significantly better than Scudo in Bionic's
real-world memory_replay traces (all times in milliseconds):
+----------------+-------+----------+
| Trace | Scudo | jemalloc |
+----------------+-------+----------+
| SQL | 27 | 21 |
| Angry Birds 2 | 2236 | 1501 |
| Camera | 4251 | 979 |
| Candy Crush | 2197 | 1325 |
| Gmail | 594 | 463 |
| Maps | 434 | 344 |
| Photos | 1330 | 477 |
| PUBG | 666 | 416 |
| surfaceflinger | 221 | 192 |
| system_server | 1921 | 1416 |
| SystemUI | 102 | 79 |
| YouTube | 363 | 294 |
+----------------+-------+----------+
jemalloc also tends to use slightly less memory than Scudo for most
traces. These tests were conducted on desktop x86 Linux with glibc and
the latest stable version of each allocator, but they should still be
relevant. RSS values in KiB:
+----------------+--------+----------+
| Trace | Scudo | jemalloc |
+----------------+--------+----------+
| Angry Birds 2 | 793948 | 746992 |
| Camera | 219372 | 251888 |
| Candy Crush | 548288 | 550148 |
| Gmail | 195236 | 193048 |
| Maps | 159860 | 159816 |
| Photos | 175436 | 171872 |
| PUBG | 233752 | 223572 |
| surfaceflinger | 94736 | 107068 |
| system_server | 471048 | 484392 |
| SystemUI | 54432 | 60740 |
| YouTube | 139376 | 142252 |
+----------------+--------+----------+
While not representative of real-world usage, jemalloc also performs
fairly well in synthetic benchmarks (all times in nanoseconds):
+-----------------+---------+----------+
| Benchmark | Scudo | jemalloc |
+-----------------+---------+----------+
| alloc 8 | 87.9 | 60.1 |
| alloc 16 | 87.9 | 60 |
| alloc 32 | 88.6 | 60.7 |
| alloc 64 | 88.6 | 59.7 |
| alloc 512 | 89.2 | 60 |
| alloc 1024 | 89.4 | 59.8 |
| alloc 8192 | 89.8 | 65.2 |
| alloc 16384 | 92.7 | 69.1 |
| alloc 32768 | 97.2 | 74 |
| alloc 65536 | 109 | 83.8 |
| alloc 131072 | 41536 | 42720 |
| alloc40x 8 | 2156 | 2556 |
| alloc40x 16 | 2155 | 2244 |
| alloc40x 32 | 2234 | 2312 |
| alloc40x 64 | 2234 | 2289 |
| alloc40x 512 | 2274 | 8171 |
| alloc40x 1024 | 2397 | 2162 |
| alloc40x 8192 | 3550 | 78880 |
| alloc40x 16384 | 3732 | 124454 |
| alloc40x 32768 | 3849 | 275460 |
| alloc40x 65536 | 4987 | 727598 |
| alloc40x 131072 | 2745207 | 3067980 |
| alloc8192 1x | 464 | 454 |
| alloc8192 2x | 510 | 488 |
| alloc8192 3x | 587 | 523 |
| alloc8192 4x | 665 | 557 |
| alloc8192 5x | 742 | 598 |
| alloc8192 6x | 818 | 633 |
| alloc8192 7x | 884 | 669 |
| alloc8192 8x | 960 | 699 |
| alloc8192 9x | 1045 | 734 |
| alloc8192 10x | 1131 | 770 |
| alloc8192 11x | 1207 | 806 |
| alloc8192 12x | 1282 | 841 |
| alloc8192 13x | 1363 | 877 |
| alloc8192 14x | 1442 | 912 |
| alloc8192 15x | 1512 | 944 |
| alloc8192 16x | 1587 | 978 |
| alloc8192 24x | 2256 | 21195 |
| alloc8192 32x | 2867 | 45446 |
| alloc8192 40x | 3522 | 71618 |
| alloc8192 48x | 4126 | 89740 |
| alloc8192 56x | 4786 | 114990 |
| alloc8192 64x | 5412 | 141082 |
| alloc8192 72x | 6049 | 170742 |
| alloc8192 80x | 6712 | 198480 |
| alloc8192 88x | 7331 | 221557 |
| alloc8192 96x | 7976 | 251462 |
| alloc8192 104x | 8581 | 281626 |
| alloc8192 112x | 9245 | 313164 |
| alloc8192 120x | 9914 | 353147 |
| alloc8192 128x | 10514 | 376625 |
| alloc8192 136x | 11187 | 408194 |
| alloc8192 144x | 11802 | 445694 |
| alloc8192 160x | 13083 | 514547 |
| alloc8192 176x | 14414 | 582501 |
| alloc8192 192x | 15746 | 654346 |
| alloc8192 208x | 17044 | 712620 |
| alloc8192 224x | 18405 | 769963 |
| alloc8192 240x | 19744 | 843969 |
| alloc8192 256x | 21160 | 917803 |
+-----------------+---------+----------+
Scudo performs fairly well for a hardened memory allocator, but we're
optimizing for performance.
Full benchmark data with graphs: https://docs.google.com/spreadsheets/d/1LG_kxaK5cI14gGtnyM-nNNmfpMdV9Vh-LtYoq7H5J4s/edit
Change-Id: Ia4901eedfaa2c9779678c5b6532979de4919ee01
|
|
tm-qpr1-release
Change-Id: Ibdbfcfa964f1ef64f3e1be4c8be1359a2021f769
|
|
Adds persistent sysprops for test infra usage, and adds the tests for
the sysprops.
The test does some fancy flocking in order to restore any existing
GWP-ASan sysprop usage in the test cleanup.
Bug: 236738714
Test: atest bionic-unit-tests
Ignore-AOSP-First: cherry-pick to internal branch
Change-Id: I8956296d39c98ce8c7dd0a703b240530d8ad48db
Merged-In: I8956296d39c98ce8c7dd0a703b240530d8ad48db
|
|
Change-Id: If556ab5fcaa0049224283e5995b61a738a2b54fa
|
|
Change-Id: Idee400376fa30c9cd0ed5b272baceddd3d938cea
|
|
t-keystone-qcom-release
Change-Id: Id98ea466b12b43aad012a484cc0849067fe4969f
|
|
Change-Id: Ia7fa5c5ae9aa3ace62c5503cec3b80588e0c1eb3
|
|
t-keystone-qcom-release
Change-Id: I3d612c0e8d34d924bc49c7b6f240041af8d113d3
|
|
Change-Id: I837388d9249cc1999fb2b4ed11f0837346116f88
|
|
Change-Id: Ia14bd6ec0be894d2ca0c54682d58293efe3063f9
|
|
Change-Id: I655dbf67fcda147e41d55a60c1a4e89ffe1892a5
|
|
tm-qpr1-release
Change-Id: I64830f76a65de48b9021f3bd6c7cae4729fe27f5
|
|
bbe7c690f1 am: 3faa5e7319
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18171741
Change-Id: Ib5ab80aa5482c7edef55b1833e9859f716f17dbd
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18171741
Change-Id: I5ca07a3e4382b744dd9497319bca7d9c8ec4b34b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
t-keystone-qcom-release
Change-Id: I5a5a621f348d9923e636e3d3597b38ffa3b0ed02
|
|
Original change: https://android-review.googlesource.com/c/platform/bionic/+/2073947
Change-Id: Id15a4a4e86f6bb05378ec1f775fb07693bd9fbda
Ignore-AOSP-First: this is an automerge
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
(cherry picked from commit 0f465478006806541d5761ba9921c108036172dc)
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18167201
Change-Id: I77a91da79ab4d4eba6b89cdaa152d754d071904f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18167201
Change-Id: I4216729b35a685a76e81887734ca1ed2ec8c5081
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
We've had complaints about ubsan issues for years, but never got to the
bottom of them, or saw them ourselves in testing. For some reason (still
not understood) we've started to see this ourselves in T and downstream
branches. So for now, let's just punch that extra hole.
Longer term, ubsan should stop needing any of this, so once
https://reviews.llvm.org/D124212 is in an LTS NDK, we should be able to
get rid of this _and_ the existing sanitizer-related holes.
Bug: https://github.com/android/ndk/issues/1298
Bug: http://b/229989971
Test: treehugger
Change-Id: Id42cb29c4e943c0080c0d34ce4e5d6d1b32da9e8
(cherry picked from commit a0745cea5f8510c6bb53dfda16dcba9cca0905d1)
Merged-In: Id42cb29c4e943c0080c0d34ce4e5d6d1b32da9e8
|
|
Change-Id: Ifbb581188c9c26b9f4742ff0aba36f0f07fe4e37
|
|
Change-Id: I35388fa85b1e14024961e02771a7a0ff7eb731e7
|
|
tm-qpr1-release
Change-Id: I993ba0ad9d8555d17b84a2381cd6071ed23ad31b
|
|
436980d31c am: b4adcec4aa
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18092494
Change-Id: I38b649c1a42fac53c2a94148e03b41b60c44b680
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
436980d31c
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/18092494
Change-Id: I16c8b93587667162c586de1fd56c9c6a73ae83b8
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Linux kernel's close_range() system call (currently) allows:
close() unshare() fcntl(F_SETFD, FD_CLOEXEC)
to be performed on ranges of fds.
All 3 of these are already allowed by seccomp bpf:
as such this doesn't allow you to do anything you can't already do.
We can't add close_range() properly to bionic because we'd need to
fiddle about with ltp and it's too late to add new T API anyway,
so let's just make the direct syscall() call.
We'll add proper support in U.
See also:
https://man7.org/linux/man-pages/man2/close_range.2.html
Test: TreeHugger
Bug: 229913920
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I85586d544fc23bed6aee59f00bdb79ee7a8150d1
Merged-In: I85586d544fc23bed6aee59f00bdb79ee7a8150d1
|
|
tm-qpr1-release
Change-Id: I874780463bc99f0276f9391f807e5a81de633291
|
|
Change-Id: I0f437ca88ec381f8cbca761f1513d17b30e535fe
|
|
06b249fc75 am: 2456232406
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/17951150
Change-Id: Ibe9c6400e6cd6c0d0fd40cf14f697e70cc0d5633
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/17951150
Change-Id: I6b687d4ea200b21fa3c82a7dfdcfe905776e76ad
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This new posix_spawn attribute flag marks all file descriptors
(except stdin/out/err) as close-on-exec before executing any user
registered file actions (posix_spawn_file_actions_addopen/adddup2).
Test: TreeHugger
Bug: 229913920
Original change: https://android-review.googlesource.com/c/platform/bionic/+/1955269
Merged-In: If458100d6a253a9b0348d4e93a9a610225f89615
Change-Id: If458100d6a253a9b0348d4e93a9a610225f89615
Signed-off-by: Maciej Żenczykowski <maze@google.com>
(cherry picked from commit fb66c0c345f17d740b6a2ef7755f768dd5bd96ee)
|
|
t-keystone-qcom-release
Change-Id: I84ecb631c23acfd3f46d3a49dea62eaba2767b41
|
|
tm-qpr1-release
Change-Id: Ib90e2810890cc8ca92a9396af896b5718419bd28
|
|
Change-Id: I383f909e71d1aacfc32324cf42d41d4132266875
|
|
Change-Id: I0fb1a7169e0000fd64598e0f802cd50602a49e0c
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/17913443
Change-Id: Idf98092719a2ab321788156be3b49044eec816c3
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/bionic/+/17913443
Change-Id: I2e461bca916f44c8b8ea95e6fd9219c71cf216b5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This value was changed from 64 to 32, but it really should not
have gone down. So fixing back to 64 manually, and then the
next kernel header update should remove the comment but leave
the value unchanged.
Bug: 228783882
Test: Compiles.
(cherry picked from commit 880308daa00c0412a2cfc598fc46ecdbbead8ff1)
Change-Id: I2d81d7bc76fcaa905dce0abb094d61d02c481a5e
|
|
tm-qpr1-release
Change-Id: Ia174a754c07dfd173bdf46ac4f1b7ec18640cb3f
|