RFR: 8267842: SIGSEGV in get_current_contended_monitor [v3]

Yasumasa Suenaga ysuenaga at openjdk.java.net
Fri May 28 12:54:05 UTC 2021


On Fri, 28 May 2021 10:13:25 GMT, Martin Doerr <mdoerr at openjdk.org> wrote:

>> We need a fix for crashes in get_current_contended_monitor due to concurrent modification of memory locations which are not declared volatile. See bug for details.
>
> Martin Doerr has updated the pull request incrementally with one additional commit since the last revision:
> 
>   New solution: Use Atomic::load/store in current_pending/waiting_monitor accessors.

Shouldn't we add `volatile` to both `_current_pending_monitor` and `_current_waiting_monitor`?

-------------

PR: https://git.openjdk.java.net/jdk/pull/4224


More information about the serviceability-dev mailing list