The second and third class, as described, do not support release/“stop wait” before acquisition. Once you start waiting you must continue waiting until you acqu

The second and third class, as described, do not support release/“stop wait” before acquisition. Once you start waiting you must continue waiting until you acquire the lock and then release otherwise it stalls forever. I imagine it might be solvable if each acquire, B, also atomically encodes its acquire criteria to the previous acquire, A, so that if A does a early release it can forward its acquire criteria to B.