Bug 1049966
| Summary: | [abrt] gvfs-smb-1.16.0-1.fc19: SMBC_stat_ctx: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Michal Toman <mtoman> |
| Component: | gvfs | Assignee: | Ondrej Holy <oholy> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | asn, dblechte, djasa, dkochuka, gdeschner, jbuchta, jwright, msimon, oholy, rvokal, svashisht, tpelka, vbenes |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| URL: | http://faf-report.itos.redhat.com/reports/420 | ||
| Whiteboard: | abrt_hash:99426e12bf64246909bcb476bfc403f32c72556e | ||
| Fixed In Version: | gvfs-1.22.4-1.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: New requests were executed on another thread during unmount operation and accessed private gvfs backend structures. It affected smb backend especially.
Consequence: Gvfs backend crashed consequently, because private structures were cleared in the meantime. It caused also nautilus crashes in some cases.
Fix: New requests are blocked and error is returned for them while the unmount is being executed.
Result: Gvfs backends are being unmounted properly without crashes.
|
Story Points: | --- |
| Clone Of: | 953622 | Environment: | |
| Last Closed: | 2015-11-19 09:25:35 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: | |||
|
Description
Michal Toman
2014-01-08 14:34:00 UTC
The same problem has been detected in Red Hat Enterprise Linux 7. The following packages are affected: gvfs-smb-1.16.4-3.el7.x86_64 The only function which frees the context and context->internal is smbc_free_context(). This function is not called inside of libsmbclient. So it must be an issue in the gvfs module. You should set the context to NULL after you've freed it. Then you should be able to find it. Let me know if I can help further. Another user experienced a similar problem: 0. Connect computer to network1 1. Connect to samba server using gnome shell Files 2. Disconnect computer from network1 3. Connect to other network2 4. Do no look on files on the connected samba 5. Disconnect computer from network2 6. Connect computer to network1 7. Try to onpen file from samba server reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-smb --spawner :1.3 /org/gtk/gvfs/exec_spaw/5 crash_function: SMBC_stat_ctx executable: /usr/libexec/gvfsd-smb kernel: 3.10.0-67.el7.x86_64 package: gvfs-smb-1.16.4-5.el7 reason: gvfsd-smb killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 I can't still reproduce exactly the same bug, however I can reproduce similar one: 1/ mount to smb using gvfs-mount 2/ execute parallel gvfs-mount -u & gvfs-ls 3/ do that several times It causes SIGSEGV in SMBC_opendir_ctx. Probaly all those bugs are race condition with unmount. If we set context = NULL when unmount, it will solve some cases by error message instead of crash, but it doesn't cover all cases... This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. *** Bug 1152595 has been marked as a duplicate of this bug. *** It seems it was fixed upstream by the commit: https://git.gnome.org/browse/gvfs/commit/?id=87c9f6d80ac612caedb7b39b22b3d4ed2804bb0b because I don't see any abrt bug report for F21... *** Bug 1215826 has been marked as a duplicate of this bug. *** The commit mentioned in the Comment 18 is included in the rebased gvfs (Bug 1174716). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2106.html |