- 11 Nov, 2015 1 commit
-
-
Jon Larimer authored
-
- 10 Nov, 2015 1 commit
-
-
William Luh authored
Bug:23180694 Change-Id: I566a290334345f48013029534efef3e08e726e40
-
- 12 Sep, 2015 2 commits
-
-
Narayan Kamath authored
* commit 'fef9dffd': Follow up to change b638126e DO NOT MERGE.
-
Narayan Kamath authored
* commit 'a82d6dc3': libutils: Fix integer overflows in VectorImpl. DO NOT MERGE
-
- 11 Sep, 2015 1 commit
-
-
Narayan Kamath authored
* commit '6c53de92': Follow up to change b638126e DO NOT MERGE.
-
- 10 Sep, 2015 2 commits
-
-
Narayan Kamath authored
Change-Id: If5062b01afa95279ab25fe86aaafa89d4d74eaa1
-
Narayan Kamath authored
Resolves delta between the kitkat and L version of this patch. Fixes the molly build on klp-dev. bug: 22953624 Change-Id: I696a506320f30d3d5cd95f6da35361244986cb36
-
- 09 Sep, 2015 2 commits
-
-
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 (cherry picked from commit c609c31f) Change-Id: I61644633db6b54fa230683615de9724f7fabf6fb
-
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 (cherry picked from commit c609c31f) Change-Id: I673b7ab142bed4fcba9159a00a65cf6bca6b1f6c
-
- 25 Aug, 2015 3 commits
-
-
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
* commit '3fe40514': [DO NOT MERGE] libutils: fix overflow in SharedBuffer
-
Sergio Giro authored
* commit '66b6eb94': [DO NOT MERGE] libutils: fix overflow in SharedBuffer
-
- 21 Aug, 2015 4 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
* 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 2 commits
-
-
Sergio Giro authored
* commit '4956c0fe': libutils: fix overflow in String8::allocFromUTF8
-
Sergio Giro authored
* commit '5b85b1d4': libutils: fix overflow in String8::allocFromUTF8
-
- 18 Aug, 2015 1 commit
-
-
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)
-
- 27 May, 2015 3 commits
-
-
Adam Lesinski authored
* commit 'e8582d65': Prevent integer overflow when allocating native_handle_t
-
Adam Lesinski authored
* commit '9bd7afc0': Prevent integer overflow when allocating native_handle_t
-
Adam Lesinski authored
User specified values of numInts and numFds can overflow and cause malloc to allocate less than we expect, causing heap corruption in subsequent operations on the allocation. Bug: 19334482 Change-Id: I43c75f536ea4c08f14ca12ca6288660fd2d1ec55
-
- 03 Nov, 2014 2 commits
-
-
Christopher Ferris authored
automerge: d7c8db12 -s ours * commit 'd7c8db12':
-
Christopher Ferris authored
automerge: e916313d * commit 'e916313d':
-
- 24 Oct, 2014 2 commits
-
-
Christopher Ferris authored
automerge: 5a69c1db -s ours * commit '5a69c1db': DO NOT MERGE Restore libcorkscrew unwinding.
-
Christopher Ferris authored
Change-Id: Ic6b18eeae43c2ef2256a0508ac60c1724385d3b0
-
- 21 Oct, 2014 1 commit
-
-
Narayan Kamath authored
SUPPORTED_ABIs is a prioritized list of all ABIs a device support, and must not vary depending on whether or not an app is emulated. bug: 18061712 Change-Id: I3ec3897d23e37c645b4d9d9e6e32aae9afff952c
-
- 20 Oct, 2014 1 commit
-
-
Adam Lesinski authored
Windows PE format doesn't have the same support for weak symbols as ELF does. The symbol android_log_id_to_name was strangely omitted from the resulting Windows executable and the callsite where it was supposed to be called was relaced with a different symbol, which caused a crash in AAPT on Windows. This change works due to a careful set of #ifdefs that ensure only one definition of android_log_id_to_name is defined, but there are other uses of __attribute__((weak)) which should be inspected. Change-Id: I3b58076e31d9b28c5143773a170e9ffda9fa3815
-
- 16 Oct, 2014 3 commits
-
-
Xavier Ducrohet authored
-
Xavier Ducrohet authored
The implementation of the FileMap destructor would close the file, only on Windows, which did not match the behavior on mac/linux. This is because calling munmap does not close the file descriptor. It must be closed separately, before or after munmap. On Windows, the file must also be closed manually, before or after closing the mappingFile. The change basically removes the closing file from the windows-specific part of the destructor, to make behavior more consistent on all platforms where the caller to FileMap is responsible for closing its own file (since FileMap receives an opened file). Change-Id: I5e3cfffbb870d5f3595802ccac57dbc1dbf1ce6e
-
Xavier Ducrohet authored
With mingw 4.8, the new default packed behavior is broken and makes zip archive fails due to unexpected misalignment in CentralDirectoryRecord. This patch uses -mno-ms-bitfields to revert to the old packed behavior. Change-Id: Ic977c841e330e19451db1d31ddb22e570a525062
-
- 15 Oct, 2014 1 commit
-
-
Dianne Hackborn authored
Change-Id: I3d98a4da9c47d83d25a11ff0ef94cfcab1feabea
-
- 14 Oct, 2014 1 commit
-
-
Dianne Hackborn authored
It looks like there were a couple problems in the code: - It would not 0-terminate the string it read, to make sure we didn't see garbage at the end. - It didn't reduce buf_len as it processes data in the buffer, so if we need to read more we will increase the buffer length to be longer than the actual available data. Also put in some logs about every thing we kill, so we can see what is going on when debugging. And add a special check for us trying to kill pid 0 for any reason, since doing so seem to be terminal to the caller. Change-Id: I2fe29bfef08938b8a2eb182475c0705c14d8d84f
-
- 10 Oct, 2014 1 commit
-
-
Daniel Rosenberg authored
There was an issue causing the fat size to shrink too small, causing a fsck check to fail. Bug: 17949028 Bug: 17761281 Change-Id: Id0207f2ab44e57ff81f5a53494b45344822a6495 Signed-off-by:
Daniel Rosenberg <drosen@google.com>
-
- 07 Oct, 2014 4 commits
-
-
Christopher Ferris authored
-
Christopher Ferris authored
The computed flattened size of the blob does not match the size used by the flatten function when the last cached entry size is not 4 byte aligned. Bug: 17873145 Change-Id: I9f9fc102d4bde4681ae977b6de5f263aaaf56708
-
Christopher Ferris authored
* commit '5a69c1db': DO NOT MERGE Restore libcorkscrew unwinding.
-
Christopher Ferris authored
* commit '290efd24': Log stack even if tombstone cannot be created.
-
- 06 Oct, 2014 1 commit
-
-
Mike Lockwood authored
-
- 02 Oct, 2014 1 commit
-
-
Mike Lockwood authored
Bug: 17674304 Change-Id: I5d31bc024fa36fedac2c0ba5c4a8b100937183ad
-