Repository navigation
Fix potential infinite recursion in HYBRID/TAILCALL VMs #25039
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| --TEST-- | ||
| VM interrupt re-armed by the interrupt handler must not stop execution from making progress | ||
| --DESCRIPTION-- | ||
| zend_test.rearm_vm_interrupt installs a zend_interrupt_function that sets | ||
| EG(vm_interrupt) again every time it runs, so an interrupt is always pending. | ||
| After handling an interrupt the VM has to run the next opline before it checks | ||
| the flag again, otherwise it calls the handler forever (or recurses until the | ||
| stack overflows). | ||
| --EXTENSIONS-- | ||
| zend_test | ||
| --INI-- | ||
| zend_test.rearm_vm_interrupt=1 | ||
| --FILE-- | ||
| <?php | ||
| function inc(int $x): int { | ||
| return $x + 1; | ||
| } | ||
|
|
||
| $n = 0; | ||
| for ($i = 0; $i < 1000; $i++) { | ||
| $n = inc($n); | ||
| } | ||
| var_dump($n); | ||
| ?> | ||
| --EXPECT-- | ||
| int(1000) |
This file contains hidden or 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or 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 hidden or 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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Here's how
ZEND_VM_ENTERandZEND_VM_LEAVEexpand across VM kinds (courtesy of claude) so you can see how the change fromZEND_VM_ENTER();toexecute_data = EG(current_execute_data); LOAD_OPLINE(); ZEND_VM_LEAVE();changes things:ZEND_VM_ENTER()ZEND_VM_LEAVE()execute_data = EG(current_execute_data); LOAD_OPLINE();thenZEND_VM_INTERRUPT_CHECK();thenZEND_VM_CONTINUE()ZEND_VM_CONTINUE()return 1return 2execute_data = EG(current_execute_data); LOAD_OPLINE(); return opline | ZEND_VM_ENTER_BITreturn opline | ZEND_VM_ENTER_BITexecute_data = EG(current_execute_data); LOAD_OPLINE();thenZEND_VM_INTERRUPT_CHECK();thenZEND_VM_CONTINUE()(musttail call to the next handler)ZEND_VM_CONTINUE()I don't understand
return 1andreturn 2on PHP 8.4's CALL VM but the rest seem correct to me.