Fix persistent stream context lifetime during shutdown - #23853
Open
morrisonlevi wants to merge 2 commits into
Open
morrisonlevi wants to merge 2 commits into
morrisonlevi wants to merge 2 commits into
Conversation
bwoebi
reviewed
Sep 25, 2026
| die("server failed: $error ($errno)\n"); | ||
| } | ||
|
|
||
| $GLOBALS['late_context_address'] = 'tcp://' . stream_socket_get_name($server, false); |
Member
There was a problem hiding this comment.
Suggested change
| $GLOBALS['late_context_address'] = 'tcp://' . stream_socket_get_name($server, false); | |
| $late_context_address = 'tcp://' . stream_socket_get_name($server, false); |
Not sure what $GLOBALS does here?
Contributor
Author
There was a problem hiding this comment.
It's just making it available so that the other user can use it. I guess it could use global $late_context_address instead?
Member
|
I think the whole problem boils down to forget_persistent_resource_id_numbers() being called too early (= module rshutdown). This simply should be called after zend_close_rsrc_list() and then there's nothing which could put anything back onto EG(persistent_list). Instead of at module rshutdown, which runs before. I.e. simply moving the call should fix the issue alltogether. |
morrisonlevi
force-pushed
the
mshutdown-stream-free
branch
from
September 26, 2026 00:16
0172cf1 to
c5536b3
Compare
Contributor
Author
|
Bob, I've updated for a simpler implementation which just nulls it in PRSHUTDOWN. Please take a look! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This problem sounds like something only a fuzzer or AI would find, but actually it's from a customer crash.
The reproducer creates a persistent stream during rshutdown and crashes during mshutdown when freeing streams, specifically when trying to access the stream context. The stream context was created in rshutdown and uses request-scoped memory, which is why it's a bad access in mshutdown.
I fix it in this patch by adding a check inAfter a bit of discussion with Bob, I'm trying a simpler patch which handles it inphp_stream_context_freewhich loop over all the resources inEG(persistent_list)and removes the context from any streams which still use the context we're freeing. We do this only if the executor is in shutdown e.g.EG(flags) & EG_FLAGS_IN_RESOURCE_SHUTDOWN, so we're not doing this during a request, only at the end of a request. Doing it only in shutdown should mitigate performance concerns.PRSHUTDOWN. As far as I can tell, it doesn't leak. The danger I see is there's a period betweenzend_destroy_rsrc_listand when this prshutdown handler runs that the stream context is a dangling pointer. In practice, that mostly seems to be other extensions' prshutdown handlers.This is my best attempt at fixing it as someone who knows little about streams. Maybe someone who knows more can find a better patch, as hopefully the reproducer is reliable across machines too.
Targeting PHP 8.4.