| Summary: | [abrt] esc-1.1.0-21.el6: __strcmp_ssse3: Process /usr/lib64/esc-1.1.0/escd was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Siddharth <swaikar> | ||||||||
| Component: | esc | Assignee: | Jack Magne <jmagne> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Chandrasekar Kannan <ckannan> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.1 | CC: | aakkiang, benl, case-diagnostics, dpal, jgalipea, jwest, rdassen, rrelyea, vgaikwad | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | esc-1.1.0-22.el6 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
Previously, during the shut down sequence of the escd daemon, the daemon reported a failure of certain instances. ESC terminated unexpectedly with a segmentation fault as a consequence. This update modifies the daemon to exit quietly. As a result, ESC no longer terminates unexpectedly.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-12-06 17:59:50 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Siddharth
2011-03-04 13:46:45 UTC
Created attachment 482291 [details]
backtrace, disassembly
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Looks like this is happening on cleanup, when the process is on the way out. Happening during CoolKey shutting down. Thanks for the report. It would help if there is some reasonable way to reproduce this. Created attachment 487224 [details]
Backtrace, Dissassembly
Created attachment 516806 [details]
Patch to address this issue.
The reason why this is occurring is that the pcsc client call "SCardCancel" is hanging when shutting down CoolKey. ESC put in some simple code to exit when it detects this hanging condition. The problem with the seg fault is addressed in ESC , but it would be better if the issue in pcsc-lite could be addressed so this hang does not occur. We have another bug filed for this issue. The reason why this is important is because when Firefox has the Coolkey pkcs#11 module loaded, it is subject to this very hanging condition. *** Bug 745169 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:
Previously, during the shut down sequence of the escd daemon, the daemon reported a failure of certain instances. ESC terminated unexpectedly with a segmentation fault as a consequence. This update modifies the daemon to exit quietly. As a result, ESC no longer terminates unexpectedly.
Executed following tests on a RHEL-6.2 i386 and x86_64 desktop with esc-1.1.0-23.el6 installed, escd does not crash. 1. Make sure "escd" is running (ps -fe | grep escd), if not launch it. 2. Use the "kill" program to send a signal to shutdown. "kill <pid-of-escd>" 3. Place a tail on the system log "tail -f /var/log/messages". 4. Upon repeated trials of this scenario, escd does not register a crash. Marking the bug verified. 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-2011-1718.html |