-
Notifications
You must be signed in to change notification settings - Fork 8k
Fix GH-19653: Closure named argument unpacking between temporary closures can cause a crash #19654
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
Closed
+65
−6
Closed
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
19ca448
Fix GH-19653: Closure named argument unpacking between temporary clos…
nielsdos 3afdb1f
review
nielsdos 27344ac
fixup review
nielsdos 3d32d6d
Fix inverted condition
nielsdos b7f2adf
Remove redundant check
nielsdos 061cc5d
Soften requirement
nielsdos 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
--TEST-- | ||
GH-19653 (Closure named argument unpacking between temporary closures can cause a crash) | ||
--CREDITS-- | ||
ivan-u7n | ||
--FILE-- | ||
<?php | ||
|
||
|
||
function func1(string $a1 = 'a1', string $a2 = 'a2', string $a3 = 'a3') { | ||
echo __FUNCTION__ . "() a1=$a1 a2=$a2 a3=$a3\n"; | ||
} | ||
|
||
function usage1(?Closure $func1 = null) { | ||
echo __FUNCTION__ . "() "; | ||
($func1 ?? func1(...))(a3: 'm3+'); | ||
} | ||
usage1(); | ||
|
||
$func1 = function (string ...$args) { | ||
echo "[function] "; | ||
func1(...$args, a2: 'm2+'); | ||
}; | ||
usage1(func1: $func1); | ||
|
||
?> | ||
--EXPECT-- | ||
usage1() func1() a1=a1 a2=a2 a3=m3+ | ||
usage1() [function] func1() a1=a1 a2=m2+ a3=m3+ |
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.
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.
fbc->op_array.opcodes
is not unique unlessZEND_ACC_IMMUTABLE
is set. E.g.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.
Good (but unfortunate) find.
This should be a rare though. What about avoiding the use of a cache slot in the case
ZEND_ACC_IMMUTABLE
is unset?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.
Yes this sounds good
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.
This also only is problematic for files and file-bound op_arrays. I.e. for anything named that's perfectly fine.
As a suggestion to avoid branching on fbc->type, you might use
fbc->common.arg_info
as key instead.Avoiding the use of a cache slot when
ZEND_ACC_IMMUTABLE
is unset essentially disables the optimization for every closure call though, which is unfortunate (as they aren't immutable at all, only the prototype is).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.
Ideally there would be a fn_flag which would indicate whether something is persistent or not.
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.
fbc->common.arg_info
can be shared among internal functions, no?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.
I suppose then it doesn't matter because functions always ahve the same argument ordering then
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.
Yeah okay this is no good.
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.
We can check that
fbc->op_array.refcount
is NULL as a proxy for "op array is persistent", but that requires branching.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.
We can do the branching on the "slow" part, i.e. when we store the data into the cache slot, and use the arg_info as unique key. I believe that should work.
Just committed that.