[ 
https://issues.apache.org/jira/browse/PROTON-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080923#comment-18080923
 ] 

ASF GitHub Bot commented on PROTON-2931:
----------------------------------------

cliffjansen commented on code in PR #444:
URL: https://github.com/apache/qpid-proton/pull/444#discussion_r3242512870


##########
c/src/proactor/epoll_raw_connection.c:
##########
@@ -110,8 +111,14 @@ static void praw_connection_start(praw_connection_t *prc, 
int fd) {
 }
 
 /* Called on initial connect, and if connection fails to try another address */
+/* May be called within the praw_connection task or from an external 
name_lookup task */
 static void praw_connection_maybe_connect_lh(praw_connection_t *prc) {
+  int err = 0;

Review Comment:
   done but first init to 0 retained with added comment



##########
c/src/proactor/epoll_raw_connection.c:
##########
@@ -161,6 +173,7 @@ static void raw_connection_lookup_done_lh(praw_connection_t 
*prc, struct addrinf
 static void raw_connection_done_cb(void *user_data, struct addrinfo *ai, int 
gai_error) {
   praw_connection_t *prc = (praw_connection_t *)user_data;
   lock(&prc->task.mutex);
+  prc->name_lookup_pending = false;

Review Comment:
   done





> Epoll proactor has race conditions with the async c-ares name resolver library
> ------------------------------------------------------------------------------
>
>                 Key: PROTON-2931
>                 URL: https://issues.apache.org/jira/browse/PROTON-2931
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: proton-c-0.41.0
>            Reporter: Clifford Jansen
>            Assignee: Clifford Jansen
>            Priority: Blocker
>
> If the c-ares callback is very quick, the pn_raw_connection_t can sometimes 
> fail to schedule itself and hang while still in the connecting phase.  This 
> can be easily reproduced with a ulimit for open files of 1024 or less and the 
> following reproducer.
>   https://github.com/fgiorgetti/router-locust
> Conversely, if the callback is extremely slow, the connection can wind up and 
> free resources before the callback tries to reference through an invalid 
> pointer.  The connection should remember if a callback is pending and defer 
> any cleanup until this concludes.  This applies to raw and AMQP connections.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to