-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix #79825: opcache.file_cache causes SIGSEGV with custom opcode hand…
…lers Modules may have changed after restart which can cause dangling pointers from custom opcode handlers in the second-level cache files. This fix includes the installed module names and versions in the accel_system_id hash as entropy. Closes GH-5836
- Loading branch information
Showing
2 changed files
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2d4aa1e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this causes a bunch of segfaults on Travis: https://travis-ci.org/github/php/php-src/jobs/725704433
2d4aa1e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nikic 🤦 Oh my god. I can't believe I missed that. I spent two hours making sure every "t" was crossed and "i" dotted since it was very first merge and I still effed it up. I'm really sorry about that! Admittedly I only ran the tests for
Zend/tests
andext/opcache/tests
for each branch marge, but that was a bad call. Next time I'll absolutely run the full suite (I keep forgetting about the new fancy parallelization!)It looks like @cmb69 fixed this in 4e198c0. Thank you for that! And again, I'm really sorry for the added hassle. 😞
2d4aa1e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries, @SammyK! :)