On Mon, 6 Jul 2020 14:02:59 +0300
Alexandru Ardelean wrote:
> Since there was a recently discovered issue with these locks, it probably
> makes sense to cleanup the code a bit, to prevent it from being used as an
> example/reference.
>
> This change moves the lock only where it is explicitly
Since there was a recently discovered issue with these locks, it probably
makes sense to cleanup the code a bit, to prevent it from being used as an
example/reference.
This change moves the lock only where it is explicitly needed to protect
resources from potential concurrent accesses.
It also
2 matches
Mail list logo
