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

Add stack-heap collision check to BrkSyscall execution #346

Merged
merged 5 commits into from
Sep 3, 2024

Conversation

federicovilla55
Copy link
Contributor

Implemented additional checking in the execute() method of the brk syscall, defined in the BrkSyscall class, to ensure that memory allocation does not overflow stack space. The System Call has as its argument the new "program break", which is now compared with the current "stack pointer" before being set to avoid overlaps.
This commit resolves a @todo present in the code.

federicovilla55 and others added 4 commits February 25, 2024 22:01
Implemented additional checking in the `execute()` method of the brk syscall, defined in the `BrkSyscall` class, to ensure that memory allocation does not overflow stack space.
The System Call has as its argument the new "program break", which is now compared with the current "stack pointer" before being set to avoid overlaps.
@mortbopet
Copy link
Owner

Awesome! And then the obligatory question of - is it possible to add a unit test for this? :)

Added unit tests to verify that when the `brk` syscall is called with illegal arguments (causing a stack-heap collision), the syscall returns a non-zero value, indicating that it was not executed successfully.
@mortbopet mortbopet merged commit d0c71e8 into mortbopet:master Sep 3, 2024
6 checks passed
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