tree cd9beedd99d35dc2b72fbb459c7176950122c74b
parent c67aed05f7c17e6e80c3d18d744861580bb74607
author Roman Elizarov <elizarov@gmail.com> 1583486601 +0300
committer GitHub <noreply@github.com> 1583486601 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeYhaJCRBK7hj4Ov3rIwAAdHIIADltzPkg+RPxdDnViN/GquxF
 fvY2u7tjCPigv3DVRD3GkQNS1f2YW+6gA6rXjq6Dw3dsrpepQZ6cTB3q7pAkVMDH
 Ip9suuFZcSMS1lNYzAs4ib8XHfOkWpAGDrQ+ypJP/CUdQf/oBLXmqCWSVyASlhOk
 OOHyIiwqzSAGg1UG2qVebRUWCQRViLXveyoe1Lm6jos/9ZiqmiOQ+LSYgwNRCE3k
 Buu8T77EZ1KIAPeV8uevebjXAUtQ3CM8pSswCkpt8YJVHQOrmkAlEz3Ms25erU8G
 /qQdyAhbdPHaQC5z3evCuHpYofX3bjI3Jpl8XgQ6vWdANMsd+DNTHCQ3e46hIKE=
 =EJDD
 -----END PGP SIGNATURE-----
 

Fixed memory leak on a race between adding/removing from lock-free list (#1845)

* The problem was introduced by #1565. When doing concurrent add+removeFirst the following can happen:
  - "add" completes, but has not correct prev pointer in next node yet
  - "removeFirst" removes freshly added element
  - "add" performs "finishAdd" that adjust prev pointer of the next node and thus removed element is pointed from the list again
* A separate LockFreeLinkedListAddRemoveStressTest is added that reproduces this problem.
* The old LockFreeLinkedListAtomicLFStressTest is refactored a bit.