Bug 1161103
| Summary: | Perl core-dumps if a hash is tied to SDBM_File before spawning a thread | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | perl | Assignee: | Petr Pisar <ppisar> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Kepler <jkejda> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.5 | CC: | bnater, fkrska, jkejda, jkurik, jorton, pm-eus, ppisar, psabata, rvokal, tbowling |
| Target Milestone: | rc | Keywords: | Patch, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://rt.perl.org/Ticket/Display.html?id=61912 | ||
| Whiteboard: | |||
| Fixed In Version: | perl-5.10.1-136.el6_6.1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Spawning threads after tying a variable to an SDBM
database using SDBM_File Perl module.
Consequence:
Perl interpreter crashes when terminating Perl threads.
Fix:
DB_File, GDBM_File, NDBM_File, ODBM_File, and SDBM_File
Perl modules have been modified to destroy their objects
only from thread context which created the objects.
Result:
DB_File, GDBM_File, NDBM_File, ODBM_File, and SDBM_File
object destructors are thread-safe now. Please
note that it does not mean that any other operations on
the objects can be called from other threads. The DB_File,
GDBM_File, NDBM_File, ODBM_File, and SDBM_File
Perl modules remain thread-unsafe in general.
|
Story Points: | --- |
| Clone Of: | 1104827 | Environment: | |
| Last Closed: | 2014-11-12 08:29:59 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: | |||
| Bug Depends On: | 1104827 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2014-11-06 11:39:24 UTC
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-2014-1849.html |