Age | Commit message (Collapse) | Author |
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11 am: 7376275cd5 am: bc9100148e am: 7a1307398a am: d860cf8b05
am: 79c71c3fc8
Change-Id: I3a3fe72195815d2195c3856127d529b74be5d5cb
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11 am: 7376275cd5 am: bc9100148e am: 7a1307398a
am: d860cf8b05
Change-Id: I023d4997293b85705c5b3401e3633d39380aef4f
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11 am: 7376275cd5 am: bc9100148e
am: 7a1307398a
Change-Id: I4a42b9c102cb46a898fd3386ea78f93c8ae04523
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11 am: 7376275cd5 am: bc9100148e
Change-Id: Ic0e208ef35cd27a58f65c1e12360a75b0fcb6963
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11 am: 7376275cd5
Change-Id: Ic065e3ff65088bfb2f0b3081654629f5e981e19f
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397 am: 52687e5f11
Change-Id: Ifa56c15c7d2b7672bc40e361d1eb6affe2212d1b
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4 am: 387016b397
Change-Id: Ibe1b077404f4b1fd8900cfb28a113f12134780c6
|
|
am: 04bc663e2b am: 1fcb8d205d am: 1cfb5670e4
Change-Id: I34bcc6aa905ea15424895d45d5d6f0ae5bb5b0b3
|
|
am: 04bc663e2b am: 1fcb8d205d
Change-Id: I3f0f9349d1b2451400fd5c7889a2aafa575b4937
|
|
am: 04bc663e2b
Change-Id: Ide7f1d3acbd3212bad50426926a223cf25e79967
|
|
Change-Id: I57b13bdc95193442aeae929a17a240c98ebfb789
|
|
Change-Id: I3fbd465fe599e0b08ec251c43c19d62bc6a451e5
|
|
If the value being printed has embedded quotes ("), then printing
those quotes could confuse other tools when parsing the value.
This is the simplest CL to fix the security issue, and we can circle
back to think about more robust escaping in a future CL.
Bug: 80436257
Test: manual
Change-Id: Ica17f2c5701573bceafe34f20110d230a3925483
|
|
Volume label name is 16 bit unicode string according to spec.
Currently blkid labels the device without converting it to
utf-8 chars due to which incorrect label is displayed.
Bug: 74184636
Test: manual
Change-Id: Ib16204c75c2cdf675d480e9c66f484bb3c51108e
|
|
am: 36876facd5
Change-Id: I0b5f6e1ed30a818589540373094cd5e7fa4f5087
|
|
am: 2d45bf8417
Change-Id: Ie193599e250f4d552277c4cb67d9f1630fe9e20a
|
|
am: f7259e7a22
Change-Id: I7dbfcf9179a12750901b6999a0eb74e2ab9e13f1
|
|
|
|
d471428695
am: 8660e822f5
Change-Id: Id9fa451774843f4f8d6cfa960c2ec21cee31e210
|
|
am: d471428695
Change-Id: I4e25e84ae33196de207686bfd1606d61608b3a22
|
|
am: 24ff14fcd1
Change-Id: I8beefa54ab8e928a4fd6ff768bca59bcdff3a2b5
|
|
|
|
Bug/Test: N/A
Change-Id: I2aae4c3185e1c36652f4005ebdd6455b07c949da
|
|
This target doesn't exist on Windows.
Fixes the following error:
build/make/core/main.mk:586: warning: Missing required dependency host_cross_mke2fs.conf from module host_cross_mke2fs defined in out/soong/Android-aosp_walleye.mk
Bug: 7456955
Test: above error no longer present
Change-Id: I278e53488ecfc4f9d5e540a70276344af06ad455
|
|
am: d40126d167
Change-Id: I973b951dca62f778d98acdbb0c15e875f6d10f04
|
|
am: 1b0bc2319d
Change-Id: Icdc24e39aa46539e643e2908c00a0a574521b25d
|
|
am: c4d54206da
Change-Id: Ied98206c92bcee3d1cbf5af578e879b8095837df
|
|
|
|
LTP tests assume existence of mkfs.ext[234] in order to create
filesystems, so we add the symbolic links.
Test: vts
Bug: 31226527
Bug: 31226662
Bug: 31226379
Bug: 31226047
Bug: 31226376
Bug: 31226714
Bug: 31226122
Bug: 31225634
Bug: 31226069
Bug: 31226031
Bug: 31225881
Bug: 31226562
Bug: 31226411
Bug: 31226410
Bug: 31226028
Bug: 31226509
Bug: 31226253
Bug: 31226404
Bug: 31226353
Bug: 31225624
Bug: 31225677
Bug: 31225191
Change-Id: I039c9e495d11dfc448f7f0de9e519394ed827d7a
|
|
When assigning physical address for new data block, search sha
of existing blocks for match. If there's a match, reuse address
of the matched block.
Also set EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS in de-duped image.
Bug: 64109868
Change-Id: I8d2d22e9c301264413c1454c84d7bf6bb32ac5c0
|
|
Also update it so that hash key can be arbitrary length instead of
null terminated string.
Bug: 64109868
Change-Id: Icb0d91d5d753e86edaffcacb043b6f1aa429a528
|
|
'lable' address." am: 58e29f870e am: 1dae5eab97
am: 3d484247a5
Change-Id: I4fa25d417656f44b80eda2d2a1a337b3b51bfbcf
|
|
'lable' address." am: 58e29f870e
am: 1dae5eab97
Change-Id: I522cb2bf2527854bb2a866b378f98875ad544f9c
|
|
'lable' address."
am: 58e29f870e
Change-Id: I9dc8f544fd6602b8040ab884e7a79ce4ed711b30
|
|
'lable' address."
|
|
'lable' address.
Avoid a potential out-of-bounds memory access address of label
Test: mma -j8 and boot devices
Change-Id: I155aa4e26f7079f517be3202de0032a86368559d
|
|
am: 6fd11f3bc9
Change-Id: Id46ba76ce888096c3f9a10190940510eb036b368
|
|
am: c010544766
Change-Id: Ie77958b71b800b232411aa4a20f890b099e82d5f
|
|
am: d8d3ba7dda
Change-Id: If1f90a80fa5adbfbb6edbe961a9f7056cb6e46e2
|
|
|
|
Hide unused parameters/variables warnings for mingw.
There are a lot of typedef redefinition errors (warnings) stemming from
linux/types.h being included after ext2_types.h
Bug: 69933068
Test: mmma external/e2fsprogs
Change-Id: Id0815e9e01f4c137fb57696f7afd37935ebd35a1
|
|
am: c1a5a9b1ab
Change-Id: I292057cb00e691aec14e67527cb9e2068d29169d
|
|
am: f99800d245
Change-Id: Ib20aaca83fa169182f473eaf90146e3c59f74c99
|
|
am: 6428ed2f85
Change-Id: Icb28dd3ec52e5f0a6fecbfb9cae0680978ec0946
|
|
|
|
In https://github.com/torvalds/linux/commit/8db6c34f1dbc8 , namespaced
file capabilities were introduced. That change updated VFS_CAP_REVISION
from VFS_CAP_REVISION_2 to VFS_CAP_REVISION_3.
Android code is written assuming v2 capabilities, and the code will
break if we naively try to treat a v2 structure as a v3 structure.
So don't even try.
Android kernels prior to v4.14 will not support this extended capability
structure, so attempting to set such capabilities will ultimately fail.
With 8db6c34f1dbc8, it appears that attempting to read a v3 capabilities
xattr will always downgrade the capability to a v2 capability, so it
really doesn't make sense to look for a v3 capability.
Android capabilities are only created at /system and /vendor filesystem
creation time by host tools. Android processes, within or outside a
namespace, are not permitted CAP_SETFCAP
(https://android-review.googlesource.com/c/platform/system/sepolicy/+/547801/1/public/domain.te
line 1101). So we should never have to deal with a v3 capability other
than those that might appear on the /system / /vendor partition at a
future date by a future author.
Bug: 69617725
Test: build/test/boot/CTS passes
Change-Id: I7f9ed62b0a539f705d697113d007f0e7379221ea
|
|
am: 65f77e6c25
Change-Id: I3ea55fa0d328d45045091d9b4815ebd02e94c106
|
|
Change-Id: Ia8304a03a78467b7965951b175adaf663c072ad7
|
|
Change-Id: If648649c7f507b88a48cea55cba4756a02c95bef
|
|
am: e3fd73e1c8 am: 5e3c7bd6d0
am: 8d1747b395
Change-Id: Ib199ae2a9f7a3baf1f5f07db7d5d245206d57dcc
|