mem: implement a stack overflow detection mechanism #293
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.
Problems
With Argobots, stack overflow can easily happen because each stack tends to be small (e.g., #274), but this overflow is often silent because there is no stack guard page. Creating an
mprotect()
-ed stack is not very trivial, but at least Argobots should employ a simple mechanism to detect it.Solution
This patch implements a stack canary that can check whether a stack overflow happens or not when a ULT is freed. This check is quite simple and lightweight. If stack overflow is detected, the runtime terminates. Please check the mechanism here: https://en.wikipedia.org/wiki/Stack_buffer_overflow#Stack_canaries
Note that this mechanism is to make sure that there is no stack overflow. This mechanism cannot pinpoint where the stack overflow happens.
This mechanism slightly degrades the performance, so it is disabled by default. It can be enabled by setting
--enable-stack-overflow-check=canary
(or--enable-stack-overflow-check=canary-XX
where XX is a large number to use a larger canary) at configuration time.Impact
This feature is disabled by default, so it will not affect the default behavior.