[gnutls-devel] GnuTLS | WIP: fixed operation under multiple threads (!935)

[Development of GNU's TLS library]

What I think we should address is the problem of a transition from A->B, is read either as A or B. A tmp variable as I understand it may not help in the case where the platform does not guarrantee atomicity in writes. That's why I think atomic will solve it. The transitions we care to protect from (RECV_STATE_FALSE_START_HANDLING, RECV_STATE_FALSE_START, and RECV_STATE_0) do not require us to use locks (i.e doesn't matter if we read HANDLING while we are in FALSE_START).

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/935#note_144630438
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20190225/a86ddff3/attachment.html>