Bug 1093314

Summary: [abrt] Crash under socket_connect_finish()
Product: [Fedora] Fedora Reporter: Ilia Gradina <ilya.gradina>
Component: libsoupAssignee: Matthew Barnes <mbarnes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: danw, fabiano, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3c13beec369eba63ae854301e16f58a4197150be
Whiteboard: abrt_hash:6dd480699591ee7d8670c942570394a0f4b1b9d4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:26:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ilia Gradina 2014-05-01 10:54:53 UTC
Version-Release number of selected component:
evolution-data-server-3.12.1-2.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: socket_connect_finish
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.15.0-0.rc1.git2.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 socket_connect_finish at /lib64/libsoup-2.4.so.1
 #1 soup_connection_connect_sync at /lib64/libsoup-2.4.so.1
 #2 soup_session_process_queue_item at /lib64/libsoup-2.4.so.1
 #3 soup_session_real_send_message at /lib64/libsoup-2.4.so.1
 #4 send_and_handle_redirection at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so
 #5 caldav_server_list_objects at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so
 #6 synchronize_cache at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so
 #7 caldav_synch_slave_loop at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so
 #8 g_thread_proxy at /lib64/libglib-2.0.so.0

Comment 1 Ilia Gradina 2014-05-01 10:54:58 UTC
Created attachment 891436 [details]
File: backtrace

Comment 2 Ilia Gradina 2014-05-01 10:55:00 UTC
Created attachment 891437 [details]
File: cgroup

Comment 3 Ilia Gradina 2014-05-01 10:55:03 UTC
Created attachment 891438 [details]
File: core_backtrace

Comment 4 Ilia Gradina 2014-05-01 10:55:05 UTC
Created attachment 891439 [details]
File: dso_list

Comment 5 Ilia Gradina 2014-05-01 10:55:07 UTC
Created attachment 891440 [details]
File: environ

Comment 6 Ilia Gradina 2014-05-01 10:55:09 UTC
Created attachment 891441 [details]
File: exploitable

Comment 7 Ilia Gradina 2014-05-01 10:55:11 UTC
Created attachment 891442 [details]
File: limits

Comment 8 Ilia Gradina 2014-05-01 10:55:14 UTC
Created attachment 891443 [details]
File: maps

Comment 9 Ilia Gradina 2014-05-01 10:55:16 UTC
Created attachment 891444 [details]
File: open_fds

Comment 10 Ilia Gradina 2014-05-01 10:55:18 UTC
Created attachment 891445 [details]
File: proc_pid_status

Comment 11 Ilia Gradina 2014-05-01 10:55:20 UTC
Created attachment 891446 [details]
File: var_log_messages

Comment 12 Milan Crha 2014-05-02 05:47:45 UTC
Dan, do you have any idea what this can be about, please? The libsoup usage code in CalDAV is pretty straightforward, though, if I'm not mistaken, then multiple threads can access the soup session, one is the synchronize thread another is the one which calls soup_session_abort(). Can that be (part of) the problem?

Comment 13 Dan Winship 2014-05-02 15:50:15 UTC
Hm... yeah, soup_socket_connect_sync_internal() doesn't hold a ref on the socket, so if another thread destroyed it while it was connecting, *boom*.

Should be an easy fix.

Comment 14 Dan Winship 2014-05-03 21:16:36 UTC
fixed upstream, will make it into rawhide with the GNOME 3.13.2 release in a bit over a week

Comment 15 Milan Crha 2014-05-05 07:41:49 UTC
Thanks. I'm moving this bug report to libsoup, as there was done the fix.

Comment 16 Jaroslav Reznik 2015-03-03 15:44:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 17 Fedora End Of Life 2016-07-19 11:26:31 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.