Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1344749 - perl segmentation fault when using PerlIO Layer :locale and threads
perl segmentation fault when using PerlIO Layer :locale and threads
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: perl-maint-list
Martin Kyral
Lenka Špačková
https://rt.perl.org/Public/Bug/Displa...
: Patch
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-10 11:47 EDT by Abhijeet Sadawarte
Modified: 2016-11-03 20:16 EDT (History)
5 users (show)

See Also:
Fixed In Version: perl-5.16.3-289.el7
Doc Type: Release Note
Doc Text:
Perl interpreter no longer crashes after using the PerlIO locale pragma When a thread was spawned after using the PerlIO locale pragma, the Perl interpreter terminated unexpectedly with a segmentation fault. An upstream patch has been applied, which fixes PerlIO::encoding object duplication. As a result, threads are correctly created after setting a file handle encoding.
Story Points: ---
Clone Of:
: 1345788 1390907 (view as bug list)
Environment:
Last Closed: 2016-11-03 20:16:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Upstream fix (5.12 KB, patch)
2016-06-13 10:00 EDT, Petr Pisar
no flags Details | Diff
Fix ported to perl-5.16.3 (4.97 KB, patch)
2016-06-13 10:44 EDT, Petr Pisar
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2191 normal SHIPPED_LIVE perl bug fix update 2016-11-03 09:19:19 EDT

  None (edit)
Description Abhijeet Sadawarte 2016-06-10 11:47:06 EDT
Description of problem:

perl segmentation fault when using PerlIO Layer :locale and threads


Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux Server release 7.2


How reproducible:

~~~~
[root@dhcp7-145 abhi]# perl
use open IO => ':locale';
use threads;
sub loop {for ($x = 1; $x < 1000000000000; $x++) {}}
$thr = threads->create(\&loop);
^d

Segmentation fault (core dumped)
~~~~


The script should not core dump but print a message like it does when run without the "open" pragma.

# perl
use threads;
sub loop {for ($x = 1; $x < 1000000000000; $x++) {}}
$thr = threads->create(\&loop);
^d
Perl exited with active threads:
        1 running and unjoined
        0 finished and unjoined
        0 running and detached


Additional info:

1. the crash is in the PUSHSTACKi(PERLSI_MAGIC); expansion

2. looks like a very old bug :( http://www.gossamer-threads.com/lists/perl/porters/219693) and it appears to have been fixed in 2015, so maybe our perl is missing it 

3. link to report is 
~~~
https://rt.perl.org/Public/Bug/Display.html?id=44887
~~~

and link to patch is 
~~~
https://rt.perl.org/Public/Ticket/Attachment/1362828/730066/0001-Properly-duplicate-PerlIO-encoding-objects.patch
~~~
Comment 2 Petr Pisar 2016-06-13 02:21:21 EDT
I confirm perl-5.16.3-286.el7.x86_64 is affected.
Comment 3 Petr Pisar 2016-06-13 10:00 EDT
Created attachment 1167501 [details]
Upstream fix
Comment 4 Petr Pisar 2016-06-13 10:44 EDT
Created attachment 1167520 [details]
Fix ported to perl-5.16.3
Comment 7 Petr Pisar 2016-06-14 06:02:28 EDT
How to test:

(1) Run the code in comment #1.
Before:
  The program segfaults.
After:
  The program successfully terminate with zero exit code.
Comment 13 errata-xmlrpc 2016-11-03 20:16:22 EDT
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-2016-2191.html

Note You need to log in before you can comment on or make changes to this bug.