Skip to content

Failure to contact GridFTP server always leads to globus_ftp_control handle leak. #10

Description

@akonstantinov

In Globus Toolkit 6.0.1506371041 while using globus_ftp_client API and trying to contact non-existing GridFTP sever brings underlying globus_ftp_control handle into (cc_handle.cc_state == GLOBUS_FTP_CONTROL_CLOSING) state. Then globus_ftp_client level callback is called before handle moves into UNCONNECTED state. And if code using API manages to call globus_ftp_client_handle_destroy fast enough it bols down to globus_l_ftp_client_quit_callback which leads to globus_ftp_client_handle.c line 1796
/* Else --> leak! */
and globus_ftp_control handle is unrecoverably leaked without any error reported and globus_ftp_client handle destroyed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions