[aarch64-port-dev ] 8153107: Unbalanced recursive locking

Andrey Petushkov andrey.petushkov at gmail.com
Mon Jun 18 16:02:58 UTC 2018

> On 18 Jun 2018, at 18:46, Andrew Haley <aph at redhat.com> wrote:
> On 06/18/2018 03:09 PM, Andrey Petushkov wrote:
>> I can, but that would only be check for regression, not the fix itself
> I do not understand.  Do you mean that out have no reproducer
> at all?  Not even this one?
> http://cr.openjdk.java.net/~aph/RecursiveLocking.java <http://cr.openjdk.java.net/~aph/RecursiveLocking.java>
This one does not work for me. In additional it’s quite hard to catch such problem using this code - it does not end any of the threads, hence you cannot rely on deadlock detection mechanism to find out whether any stale locks left.
Apparently something should be quite well hand-crafted to put enough 0-s to the stack prior to creation of the stack lock there
And as I said, I have a reproducer. It just happen that it only reproduces the problem on port-aarch32 implementation
> -- 
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-runtime-dev mailing list