Repository navigation
Detach a write request from its handle before the completion notify (#310) - #311
Merged
Merged
Conversation
This was referenced Oct 1, 2026
Merged
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Fixes #310.
io_pipe_write_cbclearedreq->ioafter notifying the handle's listeners, and a listener that disposes the request inside the notify and submits the next write there (true-async-server's log sink) frees it at once; the next request takes the same address, and the store after the notify clearedioon that in-flight request, whose completion then dereferenced a NULL handle. The request is now detached before the notify, which keeps what e821878 added the store for: a dispose after a later resume does not read a closed handle. The awaitedio_pipe_writev_cbpath had the same order and gets the same change.Evidence:
sapi/asynctest/tests/test_write_resubmit.c(true-async/php-src, branchasynctest-write-resubmit): SIGSEGV 3 of 3 onef85610, passes 3 of 3 here; the test skips itself if the allocator does not reuse the address, and it did not skip.listen_pause,listen_uafandtimer_overflowpass here.core/030built with--enable-http-server-test-hooks: SIGSEGV 2 of 2 direct runs and 3 of 3 under run-tests onef85610, passes 5 of 5 here.../../../../, which misses whenext/asyncis a symlink, as on Pause a stopped listen event instead of accepting through it (#305) #306.