JDK-8153267 : nmethod's exception cache not multi-thread safe
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-04-01
  • Updated: 2017-11-29
  • Resolved: 2016-04-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u152Fixed 9 b120Fixed
Related Reports
Relates :  
There's a concurrency problem with the nmethod���s exception cache. Readers of the cache may read stale data on weak memory platforms.

The writers of the cache are synchronized by locks, but there may be concurrent readers: The compiler runtimes use nmethod::handler_for_exception_and_pc to access the cache without locking.
Therefore, the nmethod's field _exception_cache needs to be volatile and adding new entries must be done by releasing stores. (Loading seems to be fine without acquire because there's an address dependency from the load of the cache to the usage of its contents which is sufficient to ensure ordering on all openjdk platforms.)

JDK-8143897 fixed part of the problem.
Release should not be strictly required as we have the other barrier, now. It may only produce additional false negatives on weak memory model platforms.
The _count field gets released, now. But we need acquire for the readers, too.