[
https://issues.apache.org/jira/browse/DISPATCH-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007365#comment-14007365
]
ASF subversion and git services commented on DISPATCH-46:
---------------------------------------------------------
Commit 1597126 from [~tedross] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1597126 ]
DISPATCH-46 - Don't dereference a null connector in listen
> dispatch crash when proton gets bad socket
> ------------------------------------------
>
> Key: DISPATCH-46
> URL: https://issues.apache.org/jira/browse/DISPATCH-46
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 0.2
> Reporter: michael goulish
> Fix For: 0.3
>
>
> When I attempted to connect a lot of clients to a router, I exceeded my
> process limit. Then this happens:
> 1. proton gets an invalid socket, and returns a 0 from pn_listener_accept
> 2. dispatch function thread_process_listeners takes the null and starts
> using it.
> 3. Some proton calls return silently after having gotten a null input.
> 4. dispatch passes the null to pn_transport_set_max_frame, which
> dereferences it.
> 5. router blows core. testing engineer panics. hilarity ensues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
