Skip to content

RLIMIT support - Part 2 - #847

Merged
MaciejKaszynski merged 5 commits into
eclipse-score:mainfrom
etas-contrib:rlimit_support_2
Oct 27, 2026
Merged

MaciejKaszynski merged 5 commits into
eclipse-score:mainfrom
etas-contrib:rlimit_support_2

Conversation

@NicolasFussberger

Copy link
Copy Markdown
Contributor

Adds the rlimit values to the internal flatbuffer format of the launch manager.
The values are not yet configurable via json.

This keeps - though ignores - the existing values max_memory_usage and max_cpu_usage.
There were never really supported and it was always documented in the known limitations:

  • The sandbox parameters max_memory_usage and max_cpu_usage are
    currently not supported and are ignored.

Next PR will completely remove these parameters.

For a complete example, see #785

@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-847: https://eclipse-score.github.io/lifecycle/pr-847/

//
// Members are prefixed with POSIX_ because they name the seven resource limits
// specified by POSIX.1.
enum RlimitResource : ubyte {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this also covered by config and bundled within the metadata?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not in this PR, but the next PR will make this configurable via the regular json config, which is then translated to the flatbuffer schema.
PR #785 has the complete changes, including a feature integration test that checks if rlimits were applied in the started process.

RecordProperty("Description", "Verify that the forked process exits if setting a limit fails");

config_.deployment_config.sandbox.max_cpu_usage = 500;
config_.deployment_config.sandbox.rlimits = {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testing with ITF in an qemu image would also make sense if the limits are really working

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is planned for the next PR. All changes are already in #785 but have been broken down into smaller PR for easier review.

@MaciejKaszynski MaciejKaszynski left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All open comments will be done in the next PR so merging

@MaciejKaszynski
MaciejKaszynski added this pull request to the merge queue Oct 27, 2026
Merged via the queue into eclipse-score:main with commit 5a3ebe2 Oct 27, 2026
13 of 17 checks passed
@MaciejKaszynski
MaciejKaszynski deleted the rlimit_support_2 branch October 27, 2026 09:33
@github-project-automation github-project-automation Bot moved this from Backlog to Done in LCM - Lifecycle & Health FT Oct 27, 2026

This branch is waiting to be deployed

1 waiting deployment
workflow-approval — 0328f7f6 Waiting Oct 27, 2026 by NicolasFussberger via Build and test unit-tests-x86_64-qnx / approval #1823
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants