- 29 Sep, 2015 1 commit
-
-
Narayan Kamath authored
Use external/safe-iop to check for overflows on arithmetic operations. Also remove an unnecessary copy of Vector/SharedBuffer from codeflinger and use the copy from libutils instead. Note that some of the unit tests are somewhat useless due to test-runner limitations : gtest's ability to filter on abort message doesn't work when combined with messages formatted by android's logging system. bug: 22953624 Change-Id: I46b1ae8ca1f3a010be13aca36a091e76a97a7b70
-
- 27 Aug, 2015 2 commits
-
-
The Android Automerger authored
-
Bart Sears authored
* commit '170bde83': libutils: fix overflow in SharedBuffer [DO NOT MERGE]
-
- 26 Aug, 2015 2 commits
-
-
Abhishek Arya authored
-
Bart Sears authored
Change-Id: I236367bd60046ba06669cbcdae81184f9d0a74c7
-
- 25 Aug, 2015 10 commits
-
-
Sergio Giro authored
* commit '1dda45c7': libutils: fix overflow in SharedBuffer [DO NOT MERGE]
-
Sergio Giro authored
* commit '0cc9a6e6': libutils: fix overflow in SharedBuffer [DO NOT MERGE]
-
Sergio Giro authored
See https://code.google.com/p/android/issues/detail?id=181910 Bug: 22952485 (cherry picked from commit 66b6eb94) Change-Id: I363f49b5b3c6b7b3ac08cba2c14d72c431588c5a
-
Sergio Giro authored
See https://code.google.com/p/android/issues/detail?id=181910 Bug: 22952485 (cherry picked from commit 66b6eb94) Change-Id: Ic71dd0025b9a7588c4f3bb1c7be1bd13d2ff5105
-
Sergio Giro authored
am ca15dfd0: am 3fe40514: (-s ours) am 66b6eb94: [DO NOT MERGE] libutils: fix overflow in SharedBuffer * commit 'ca15dfd0': [DO NOT MERGE] libutils: fix overflow in SharedBuffer
-
Sergio Giro authored
* commit '3fe40514': [DO NOT MERGE] libutils: fix overflow in SharedBuffer
-
Sergio Giro authored
* commit '66b6eb94': [DO NOT MERGE] libutils: fix overflow in SharedBuffer
- 22 Aug, 2015 1 commit
-
-
The Android Automerger authored
-
- 21 Aug, 2015 8 commits
-
-
Sergio Giro authored
See https://code.google.com/p/android/issues/detail?id=181910 Bug: 22952485 (cherry picked from commit 7987b835) Change-Id: I3cac87185f209dc79678ae702aa18afbdf4190df
-
Abhishek Arya authored
am d34846b7: am cd407a17: am e0dce90b: Fix compile failure after rIfe1dc0791040150132bea6884f1e6c8d31972d1b * commit 'd34846b7': Fix compile failure after rIfe1dc0791040150132bea6884f1e6c8d31972d1b
-
Abhishek Arya authored
* commit 'cd407a17': Fix compile failure after rIfe1dc0791040150132bea6884f1e6c8d31972d1b
-
Abhishek Arya authored
* commit 'e0dce90b': Fix compile failure after rIfe1dc0791040150132bea6884f1e6c8d31972d1b
-
Abhishek Arya authored
Bug: 23290056 Change-Id: If6e22b0159de6635a8ca5305895b7718f15becc7
-
- 20 Aug, 2015 7 commits
-
-
Sergio Giro authored
* commit 'e67b5848': libutils: fix overflow in String8::allocFromUTF8
-
Sergio Giro authored
* commit '4956c0fe': libutils: fix overflow in String8::allocFromUTF8
-
Sergio Giro authored
* commit '5b85b1d4': libutils: fix overflow in String8::allocFromUTF8
-
Christopher Ferris authored
The dlopen of a shared library in an apk results in large map offsets. Unfortunately, the current way that the frame data is printed, it's impossible to tell what the relative pc is relative to. With the addition of the offset, it's possible to figure out what the relative pc actually references. Bug: 23348999 Change-Id: Ia51b669ea3f810158cfd0d71d9ae89bf9a3170d3
- 19 Aug, 2015 1 commit
-
-
The Android Automerger authored
-
- 18 Aug, 2015 3 commits
-
-
Sergio Giro authored
Patch contributed in: https://code.google.com/p/android/issues/detail?id=182908 Bug: 23290056 (cherry picked from commit 4eeacbee) Change-Id: Ife1dc0791040150132bea6884f1e6c8d31972d1b (cherry picked from commit ebabef27)
-
Sergio Giro authored
-
Sergio Giro authored
Patch contributed in: https://code.google.com/p/android/issues/detail?id=182908 Bug: 23290056 (cherry picked from commit 4eeacbee) Change-Id: Ife1dc0791040150132bea6884f1e6c8d31972d1b
-
- 08 Aug, 2015 1 commit
-
-
The Android Automerger authored
-
- 06 Aug, 2015 2 commits
-
-
Andres Morales authored
-
Jeff Sharkey authored
We have a bunch of magic that mounts the correct view of storage access based on the runtime permissions of an app, but we forgot to protect the real underlying data sources; oops. This series of changes just bumps the directory heirarchy one level to give us /mnt/runtime which we can mask off as 0700 to prevent people from jumping to the exposed internals. Also add CTS tests to verify that we're protecting access to internal mount points like this. Bug: 22964288 Change-Id: I32068e63a3362b37e8ebca1418f900bb8537b498
-
- 05 Aug, 2015 1 commit
-
-
Andres Morales authored
Bug: 22257554 Change-Id: I1a363729b449a2bc8594b48dada719fd79da7036
-
- 29 Jul, 2015 1 commit
-
-
The Android Automerger authored
-