| Summary: | [abrt] gnome-keyring-2.28.2-6.el6: sec_free: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | prashant ingale <pingale> |
| Component: | gnome-keyring | Assignee: | Tomáš Bžatek <tbzatek> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3 | CC: | m_roark, nalayil, sgraf, tpelka, tsmetana, vgaikwad |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gnome-keyring-2.28.2-7.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Missing thread locking mechanism
Consequence: Random crashes/asserts/aborts on multiple integrated ssh-agent key requests
Fix: Thread locks have been put in place
Result: No more crashes on multiple requests at a same time
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 14:04:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 708919, 767520, 784500 | ||
|
Description
prashant ingale
2011-10-13 05:28:25 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. *** Bug 784500 has been marked as a duplicate of this bug. *** Package: gnome-keyring-2.28.2-6.el6 Architecture: x86_64 OS Release: Red Hat Enterprise Linux Workstation release 6.2 (Santiago) Comment ----- I did 4 ssh connections in parallel, using password authentication. I had a kerberos ticket and SSH was probably trying it first. Package: gnome-keyring-2.28.2-6.el6 Architecture: x86_64 OS Release: Red Hat Enterprise Linux Workstation release 6.2 (Santiago) Comment ----- Perform 4 ssh connections in parallel (using terminator). Recent packages changes from yum.log: Feb 14 10:44:46 Installed: gitk-1.7.1-2.el6_0.1.noarch Feb 14 10:47:21 Updated: kernel-firmware-2.6.32-220.4.2.el6.noarch Feb 14 10:47:22 Updated: httpd-tools-2.2.15-15.el6_2.1.x86_64 Feb 14 10:47:26 Updated: httpd-2.2.15-15.el6_2.1.x86_64 Feb 14 10:47:44 Updated: selinux-policy-3.7.19-126.el6_2.6.noarch Feb 14 10:48:04 Updated: selinux-policy-targeted-3.7.19-126.el6_2.6.noarch Feb 14 10:48:05 Updated: httpd-manual-2.2.15-15.el6_2.1.noarch Feb 14 10:48:12 Installed: kernel-2.6.32-220.4.2.el6.x86_64 Feb 14 10:48:28 Installed: kernel-devel-2.6.32-220.4.2.el6.x86_64 Feb 14 10:48:30 Updated: kernel-headers-2.6.32-220.4.2.el6.x86_64 How to test: 1. generate private key pair, set it up for ssh authentication for another local account (using "test" here) 2. for i in `seq 1 1000`; do (ssh localhost -l test id&); done 3. make sure it prints the `id` output: "uid=500(test) gid=500(test) groups=500(test)" --> no crash/abort/assertion should show up, the gnome-keyring-daemon process should survive the torture test *** Bug 796806 has been marked as a duplicate of this bug. *** *** Bug 767520 has been marked as a duplicate of this bug. *** *** Bug 771589 has been marked as a duplicate of this bug. *** *** Bug 773712 has been marked as a duplicate of this bug. ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: Missing thread locking mechanism
Consequence: Random crashes/asserts/aborts on multiple integrated ssh-agent key requests
Fix: Thread locks have been put in place
Result: No more crashes on multiple requests at a same time
*** Bug 802256 has been marked as a duplicate of this bug. *** 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. http://rhn.redhat.com/errata/RHBA-2012-0878.html |