ZipFile: Never change file offset during I/O operations.
Use pread instead read and eliminate unnecessary calls to lseek.
dalvik.system.VMClassLoader maintains a cache of JarFile objects
that it creates whenever it loads resources from them. This cache may
be populated in the zygote as a side effect of preloading classes. When
processes are forked from the zygote, the file descriptors associated
with these JarFile objects point to the same kernel file description
and may end up stepping on each others toes. To avoid such issues, we
never make any offset changes to the associated file.
Note that we have a guarantee that the file will never be closed in
any forked process because the associated JarFile objects can never be
test: run cts -m CtsLibcoreTestCases / ZipStressTest / manual testing
to trigger the race condition.
(cherry picked from commit 0393d3c84ed9bd24bcf0dac3782a1cc23400ace8)
(cherry picked from commit 50c5924a4a1f78b7722d97dc958317027e25e214)
(cherry picked from commit 36d074286912d876489c6ff21bc0c41016180dad)
4 files changed