RFR (S) 8250844: Make sure {type, obj}ArrayOopDesc accessors check the bounds
Aleksey Shipilev
shade at redhat.com
Thu Jul 30 19:03:58 UTC 2020
RFE:
https://bugs.openjdk.java.net/browse/JDK-8250844
I was debugging some new VM patch, and figured it was a memory stomp due to wrong index passed to
objArrayOopDesc::obj_at_put. That method does not assert the index at all, which hides the errors
and silently corrupts the heap, until something else discovers it. Some objArrayOopDesc accessors do
verify the index against the bounds. Same thing goes for typeArrayOopDesc.
Fix:
https://cr.openjdk.java.net/~shade/8250844/webrev.01/
Testing: tier{1,2} locally; jdk-submit (running)
--
Thanks,
-Aleksey
More information about the hotspot-runtime-dev
mailing list