Age | Commit message (Collapse) | Author |
|
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
|
|
Change-Id: I82ffef3e0bd25783e4905f6e3d0a2be6f958f0e6
|
|
am: 65f77e6c25
Change-Id: I3ea55fa0d328d45045091d9b4815ebd02e94c106
|
|
Change-Id: Ia8304a03a78467b7965951b175adaf663c072ad7
|
|
Change-Id: If648649c7f507b88a48cea55cba4756a02c95bef
|
|
Change-Id: Iedefbe2c5cbd3761fa9f7b0df7990b6b1f121ac7
|
|
am: e3fd73e1c8 am: 5e3c7bd6d0
am: 8d1747b395
Change-Id: Ib199ae2a9f7a3baf1f5f07db7d5d245206d57dcc
|
|
am: e3fd73e1c8
am: 5e3c7bd6d0
Change-Id: I396705354c8e8ab7c19e5ce7a5aac869c802411d
|
|
am: e3fd73e1c8
Change-Id: Idbbb125e5b57d4697619561a72205ed70afd75ed
|
|
|
|
Bug: http://b/66996870
Bug: http://b/67046543
Test: Built aosp_sailfish successfully.
Change-Id: Ie527b8f4d2917f226c6379bc5873a14d51782ecd
|
|
am: fa27ed1dd1
Change-Id: Ib6ebab51d67c82d2c93c3f4302e6c98b1ed623c1
|
|
am: 22f7401cd7
Change-Id: I06a72562cad1340fceef095b4bdf4d4472b84d4c
|
|
am: 2e1e7bd962
Change-Id: I9915e04242b5e404c53c810822b91e199c90df59
|
|
* changes:
Fix build warnings with '__bitwise' macro redefined
Remove fsstress from build
|
|
external/e2fsprogs/lib/blkid/blkid_types.h:30:9:
warning: '__bitwise' macro redefined [-Wmacro-redefined]
external/e2fsprogs/lib/ext2fs/ext2_types.h:30:9:
warning: '__bitwise' macro redefined [-Wmacro-redefined]
Bug: 67046543
Change-Id: Ic8a552f68e6e17be4bdca63e24b45f6c9a6dbcd7
|
|
This is outdated and deprecated by android-xfstests
http://thunk.org/android-xfstests
Bug: 67046543
Change-Id: Ic80d5636bc06420f92ee2400bada5b7eb5595253
|
|
Change-Id: I32447451cfd4aa4878c1e5c3f1597db73a095139
|
|
246e852f81
am: 96be690dcd
Change-Id: I621f027decbc5a242f0c0061d3f617ada649c55c
|
|
am: 246e852f81
Change-Id: I9964b91b4bc37b8b03f80f3b89f467e61e4a1321
|
|
am: f5efc9e047
Change-Id: Ic40fed396f4f20ddb6f1e94b3183cab1c422f153
|
|
|
|
There is a heap buffer overflow that the next toolchain detects on
e2fsdroid. In order to expedite deploying that toolchain, which has been
validated on all of our other targets, we are going to suppress
host sanitization of this executable until we can resolve the actual
bug.
Bug: http://b/68387795
Test: ASAN_OPTIONS=detect_leaks=0 SANITIZE_HOST=address m -j48
Change-Id: I35126c25a65304e53a18031d99334cc57e21a6a5
|
|
Change-Id: If24a73ede476113f9604109340e0767f6fac10d2
|
|
89227d2f4a
am: 8da4168b0c
Change-Id: Ia5c4e2d772cca666a42ac3617bb8f10081b2aa19
|
|
am: 89227d2f4a
Change-Id: I1ae64608bd300c7b652fb55becacd464adbfacb9
|
|
am: 3db011ff8f
Change-Id: Id8b087e980ba530d80abb45fa743c64e9a6215c1
|
|
am: 3281e889db
Change-Id: Iac75de97870717ce3de580d8d20c91a21af9e3ae
|
|
|
|
* Share common flags in e2fsprogs-defaults.
* -Wno-error=macro-redefined cannot be used for windows gcc cross compiler.
* Suppress some non-critical warnings.
* Use -Wno-error for darwin; to fix mac specific warnings later.
Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: I3842bd72cdb24ca51a0a42685a33a0ce082f9c77
|
|
Change-Id: I9bc3c8b8257013f62c22c19512269bbb711c1652
|
|
84c6970f38 am: f1b45d9143
am: fa9a3325e0
Change-Id: I84acd973962c04ec0834513bac87e70bf3fa385c
|
|
5945c16bad
am: 5925478992
Change-Id: I5daf9abf011d85a49aabca7db63a07a3597a6a08
|
|
am: f1b45d9143
Change-Id: Ib711a81687a9b2d4de018d63b6519af0917aa1fa
|
|
am: 5945c16bad
Change-Id: I6551a07961db193c45abc436227a7001b721a81a
|
|
am: 84c6970f38
Change-Id: I6bcb926a209d170ef4ffe8b5b5846f277dceb45b
|
|
am: f8ee9e2f8e
Change-Id: I647ae1097fc8756971424bd3aa3cb37991045ca5
|
|
am: 0a4eaed4e0
Change-Id: I85afefe501846cfb62c6eab3909a06b6d5a414eb
|
|
am: b3b2b3000b
Change-Id: I207793b99436a176d5e4fdbf7f290fdd31c7c776
|
|
|
|
This reverts commit cd9d95f5c42375d004eb35daa42a1004365d9fae.
Change-Id: I16e52d4088c5b85dd23de519cb5af8aefeef85e6
|
|
|
|
* Share common flags in e2fsprogs-defaults.
* -Wno-error=macro-redefined cannot be used for windows gcc cross compiler.
* Suppress some non-critical warnings.
Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: I0518f65dcd7eefabe53e09909acccc91b20dd61e
|
|
135 snap-temp-L93500000107644030
Change-Id: I947f66ea2590befe0ce7cd69116103b2f2bef7dd
|
|
am: e4da3f1917
Change-Id: I6f89bd9c24ad4d559379ab45e4140076ab50761d
|
|
am: fd69531142
Change-Id: I469f79b6b637330a6f41b4f040a81d33b3f35f59
|
|
am: 9e278d6b1a
Change-Id: I356d824dcddf9c28676e61bc3f18c9910b9ec38f
|