[
https://issues.apache.org/jira/browse/PROTON-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1538:
--------------------------------
Fix Version/s: (was: proton-j-0.18.0)
proton-c-0.18.0
> Epoll proactor unguarded memory access
> --------------------------------------
>
> Key: PROTON-1538
> URL: https://issues.apache.org/jira/browse/PROTON-1538
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.18.0
> Reporter: Cliff Jansen
> Assignee: Cliff Jansen
> Fix For: proton-c-0.18.0
>
>
> ThreadSanitizer singled out the epoll_event for network sockets to be a risk
> of out of order access by multiple threads.
> On inspection it is possible that two threads could try rearming the socket
> out of order, allowing the wrong events of interest to be registered.
> Reusing the existing connection context mutex would be costly for
> guarding this since the system call is frequent and relatively long
> compared to other acquisitions of the mutex. Adding a new mutex that
> guards this operation should fix things with negligible performance
> cost.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
