opcache crashes on Ubuntu 21.10 - php 8.0.8 (segfault) both within apache2 and cli
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| php-defaults (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
| Impish |
Triaged
|
Low
|
Unassigned | ||
Bug Description
bug description : see details on https:/
segfault with opcache enabled ...
with Ubuntu 21.10 php 8.0.8 : bug occurs...
with Ubuntu 22.04 alpha php 8.1.0 : no bug!
nikic suggested to me to report this on the Ubuntu bugtracker, so you can backport whatever patch is necessary...
has been tested ok with php 8.0.16
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: php 2:8.0+82~0build1
ProcVersionSign
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: LXDE
Date: Sat Mar 12 23:02:31 2022
InstallationDate: Installed on 2022-03-04 (8 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013)
PackageArchitec
SourcePackage: php-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
| pk (pk-fr) wrote | #1 |
| Sergio Durigan Junior (sergiodj) wrote | #2 |
| Changed in php-defaults (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in php-defaults (Ubuntu Impish): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in php-defaults (Ubuntu): | |
| status: | Triaged → Fix Released |
| pk (pk-fr) wrote | #3 |
| Bryce Harrington (bryce) wrote | #4 |
Thank you for your bug report.
I could indeed reproduce the problem here by following your instructions from the upstream bug. For those coming after me:
$ lxc launch ubuntu-daily:impish php-bug1964687
$ lxc shell php-bug1964687
# apt update && apt install -y php
# cat > 1.php << EOF
<?php
echo "before<br>";
include "obfuscated.php";
echo "after<br>";
?>
EOF
# (grab the contents of https:/
# sed -i -e 's@^;opcache\
Unfortunately, this seems to me like a low priority bug, especially considering that we're nearing Impish's EOL (which will happen in June). Unless you can point us to an upstream patch that fixes this issue, I find it unlikely that a member of our team will have the time to investigate this issue soon. If you are interested and have the time, we certainly encourage bug reporters and community members to drive the process of SRU'ing a fix in this case. Let us know if you would like to do that.
Thanks.