Skip to content

Conversation

@Harshdhall01
Copy link

Fixes unikraft/unikraft#1693

This PR resolves the stack overflow issue when enabling LIBPOSIX_PROCESS_SIGNAL by increasing the default stack size configuration in the base library.

Problem: Applications using signal handling would crash with guard page violations due to insufficient stack space.

Solution: Increased CONFIG_STACK_SIZE_PAGE_ORDER and CONFIG_AUXSTACK_SIZE_PAGE_ORDER to 5, providing 512KB stack space.

Testing: Verified that the tokio1-rust1.75 example now runs successfully without stack overflow errors.

Increase default stack size to prevent overflow when signal
handling is enabled. This resolves unikraft/unikraft#1693.

Changes:
- Set CONFIG_STACK_SIZE_PAGE_ORDER to 5 (512KB)
- Set CONFIG_AUXSTACK_SIZE_PAGE_ORDER to 5 (512KB)

Tested with tokio1-rust1.75 example - now runs successfully
without guard page violations.
@Harshdhall01
Copy link
Author

Hi @razvand!

Just linking back to our conversation on unikraft/unikraft#1693 - this PR
is the catalog fix you mentioned.

This implements the interim workaround for the stack overflow issue by
bumping the stack size configuration in catalog/library/base, as suggested
by @michpappas.

Ready for review whenever you have time. Let me know if you'd like any
changes!

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.

Stack overflow when enabling LIBPOSIX_PROCESS_SIGNAL

1 participant