commit | 57da3c822d6994ed2da78cee9e2530ce263c2c75 | [log] [tgz] |
---|---|---|
author | Daulet Zhanguzin <dauletz@google.com> | Fri Aug 21 13:35:30 2020 +0100 |
committer | Daulet Zhanguzin <dauletz@google.com> | Fri Aug 21 13:35:30 2020 +0100 |
tree | dab5913a07e54f09b4c6d4b91d34c50a9f6b0480 | |
parent | e182cbceda4ee8d7cd6ca7852f5953236b3f6bc0 [diff] |
Fix reading large file offsets on 32-bit No 32 bit device on hand to verify, but this fix has been verified by partner. Test: Treehugger Bug: 156027158 (cherry pick from aosp) Change-Id: Ia604e7aac6cdd1cb46d5f2bcdf7f96cb56349954 Merged-In: Ia604e7aac6cdd1cb46d5f2bcdf7f96cb56349954
diff --git a/ojluni/src/main/native/zip_util.c b/ojluni/src/main/native/zip_util.c index 6c02d2b..aa9c5ce 100644 --- a/ojluni/src/main/native/zip_util.c +++ b/ojluni/src/main/native/zip_util.c
@@ -156,7 +156,7 @@ * JVM_IO_INTR is tricky and could cause undesired side effect. So we decided * to simply call "read" on Solaris/Linux. See details in bug 6304463. */ - return pread(zfd, buf, nbytes, offset); + return pread64(zfd, buf, nbytes, offset); #endif }