Bug 1344578 - Segmentation fault while header_register_callback
Summary: Segmentation fault while header_register_callback
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: php
Version: 7.2
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Web Stack Team
QA Contact: David Kutálek
URL:
Whiteboard:
Depends On:
Blocks: 1346758
TreeView+ depends on / blocked
 
Reported: 2016-06-10 05:21 UTC by Hisanobu Okuda
Modified: 2016-11-03 21:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, an incorrect logic in the SAPI header callback routine caused that the callback counter was not incremented. Consequently, when a script included a header callback, it could terminate unexpectedly with a segmentation fault. With this update, the callback counter is properly managed, and scripts with a header callback implementation work as expected.
Clone Of:
: 1346758 (view as bug list)
Environment:
Last Closed: 2016-11-03 21:04:57 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2598 normal SHIPPED_LIVE Moderate: php security and bug fix update 2016-11-03 12:12:00 UTC
PHP Bug Tracker 66375 None None None 2016-06-10 09:01:16 UTC
PHP Bug Tracker 66418 None None None 2016-06-10 09:00:51 UTC

Description Hisanobu Okuda 2016-06-10 05:21:37 UTC 
Description of problem:
The customer is hitting [1]. Applying the tentative fix [2], the issue was gone.
Please backport the fix.

[1] https://bugs.php.net/bug.php?id=66418
[2] https://github.com/php/php-src/commit/3c3ff434329d2f505b00a79bacfdef95ca96f0d2?diff=split

Version-Release number of selected component (if applicable):
php-5.4.16-36.1.el7_2.1.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 18 errata-xmlrpc 2016-11-03 21:04:57 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/RHSA-2016-2598.html
Note You need to log in before you can comment on or make changes to this bug.