Bug 1223045

Summary: glob in threads is broken
Product: Red Hat Enterprise Linux 7 Reporter: Paulo Andrade <pandrade>
Component: perlAssignee: Petr Šabata <psabata>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: medium Docs Contact: Lenka Špačková <lkuprova>
Priority: medium    
Version: 7.1CC: isenfeld, mkyral, ovasik, ppisar, psabata
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: All   
URL: https://rt.perl.org/Public/Bug/Display.html?id=117823
Fixed In Version: perl-5.16.3-287.el7 Doc Type: Release Note
Doc Text:
Perl interpreter no longer crashes when using glob() with a threaded program Previously, when calling the Perl glob() function after spawning a thread, the Perl interpreter terminated unexpectedly with a segmentation fault. An upstream patch has been applied to clone glob() interpreter-wide data, and using Perl glob() with a threaded program now works as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 00:15:43 UTC Type: Bug
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: 1203710, 1313485, 1289025, 1295829    
Description Flags
File::Glob: Dup glob state in CLONE() none

Description Paulo Andrade 2015-05-19 16:46:32 UTC
Upstream bug report:

Upstream patch:

For easier visualization, and cut&paste, reproducer
repeated here:

use warnings;
use strict;
use threads;
use threads::shared;
my $nthread = 20;
sub work {
    foreach (1..10000) {
	my @files = <*.supp>;
my @threads;
foreach my $i (1..$nthread) {
    push @threads, threads->create(\&work);
foreach my $t (@threads) {

Comment 3 Petr Šabata 2015-09-02 15:43:33 UTC
Created attachment 1069481 [details]
File::Glob: Dup glob state in CLONE()

Backport of the proposed patch for 5.16.3.

Comment 5 Petr Šabata 2016-03-02 15:04:58 UTC
Pushed as perl-5.16.3-287.el7.

Comment 12 errata-xmlrpc 2016-11-04 00:15:43 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.