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.
but, is there any guarantee that
s_validate_sid(which is given thePS(id)as a paremeter) doesn't make it falsey, either directly or by accessing the global?It looks like the chain of zend_string_release_ex and on don't actually assert that the string is present - can I suggest adding a
ZEND_ASSERT(PS(id))so that if there is ever a case where the string is absent at least there is a clear failure in debug builds?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.
That would be a violation of the API contract, and it requires someone to write a session storage module that purposefully fucks around with it.
I was working on trying to reduce the amount of global state in ext/session to limit those sort of problems.