Skip to content
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

Workaround 5.0 asan findings #44

Merged
merged 1 commit into from
May 17, 2019
Merged

Conversation

deweerdt
Copy link
Member

Make 16 the arrays explicitly 16 bytes large so that reads exceeding
them aren't flag as out of bounds reads

Make 16 the arrays explicitly 16 bytes large so that reads exceeding
them aren't flag as out of bounds reads
@deweerdt
Copy link
Member Author

I don't believe it's necessary to pull the change, but i figured that i would at least document the fact that ASAN reports out-of-bounds reads on range2 and range1 because while there's technically valid memory after the variable, this is still a read after the variable in question.

@kazuho kazuho merged commit 8040379 into h2o:master May 17, 2019
kazuho added a commit that referenced this pull request May 17, 2019
Fix theoretical SEGV concern (Workaround 5.0 asan findings)
@kazuho
Copy link
Member

kazuho commented May 17, 2019

Thanks for the PR. I think we have a theoretical possibility of seeing SEGV due to ALIGN(16) being absent for ranges1, though in practice people would be noticing the issue in such case because parsing would never succeed in such case.

Hence merged with cc4df34 being added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants