Martijn Coenen 057269956b Don't pad before calling writeInPlace(). ... writeInplace() itself already pads securely, by masking off the padded bytes. If the padding is done before calling writeInplace(), no mask is applied, and heap data can leak. Bug: 77237570 Test: builds Change-Id: Ide27a0002d4ed4196530430760245b971f6a3f44 Merged-In: Ide27a0002d4ed4196530430760245b971f6a3f44 (cherry picked from commit f8542381b72a7bb2452a5278a00ca8c34edbf8a0) (cherry picked from commit 732132b765cd7b667f16cf32f0fe4c852d7d44dd) Change-Id: Id65e4573e18ab68b804f1cf63a6977a71da01e5d		2018-07-16 20:24:36 +02:00
..
binder	Don't pad before calling writeInPlace().	2018-07-16 20:24:36 +02:00
diskusage	Add missing <unistd.h> include for close.	2015-02-19 16:58:44 -08:00
gui	libgui: check for invalid slot in attachBuffer	2017-07-06 21:41:47 +02:00
input	add number constraint for samples per MotionEvent am: 5d17838ade am: 72c8ca4a01 am: 9964d83869 am: 90dc6dc825	2015-10-22 22:28:01 +00:00
ui	ui: Fix bad size check in Fence::unflatten	2017-07-06 21:37:51 +02:00