diff options
| author | Alex Light <allight@google.com> | 2018-03-05 17:48:48 -0800 |
|---|---|---|
| committer | Alex Light <allight@google.com> | 2018-03-06 13:34:13 -0800 |
| commit | 18e14b5029ccac1cce609250b97bf17ebcbf128c (patch) | |
| tree | 087ad9f61a95c92506070c135d22a7965b2301b4 /libartbase/base/unix_file/random_access_file_utils.h | |
| parent | 63354d1597b8db8db2f9fb887fcf8de6e98acb70 (diff) | |
Ensure when NotifyMethodRedefined is called the ArtMethod is valid
Previously we were calling Jit::JitCodeCache::NotifyMethodRedefined
with an ArtMethod that was not fully valid. This could cause OOB
memory accesses if NotifyMethodRedefined attempts to access the
incorrect dex-file associated with the method at that time. This
occurs if the method is a native method. By looking at the wrong dex
file the JIT will get an incorrect MethodID and Shorty meaning it is
unable to correctly update the jit-code-cache.
Test: ./test.py --host -j50
Test: Run WIP dexmaker tests that hit this issue.
Bug: 74116990
Change-Id: Ied035b01b07d595df4037352b4bd20b42d285cb9
(cherry picked from commit 035105ff976680f11fa4fb12f1d42e2b7e250503)
Diffstat (limited to 'libartbase/base/unix_file/random_access_file_utils.h')
0 files changed, 0 insertions, 0 deletions