Skip to content

jailer: Use O_NOFOLLOW for cgroup and netns file operations#5811

Open
ilstam wants to merge 1 commit intofirecracker-microvm:mainfrom
ilstam:jailer-symlink
Open

jailer: Use O_NOFOLLOW for cgroup and netns file operations#5811
ilstam wants to merge 1 commit intofirecracker-microvm:mainfrom
ilstam:jailer-symlink

Conversation

@ilstam
Copy link
Copy Markdown
Contributor

@ilstam ilstam commented Apr 2, 2026

Open cgroup files in writeln_special()/readln_special() and the network namespace file in join_netns() with O_NOFOLLOW, consistent with the existing pattern used for the exec file copy in env.rs.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

Open cgroup files in writeln_special()/readln_special() and the
network namespace file in join_netns() with O_NOFOLLOW, consistent
with the existing pattern used for the exec file copy in env.rs.

Signed-off-by: Ilias Stamatis <ilstam@amazon.com>
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.00%. Comparing base (8b55c86) to head (7722212).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5811   +/-   ##
=======================================
  Coverage   83.00%   83.00%           
=======================================
  Files         275      275           
  Lines       29383    29399   +16     
=======================================
+ Hits        24388    24404   +16     
  Misses       4995     4995           
Flag Coverage Δ
5.10-m5n.metal 83.32% <100.00%> (+0.01%) ⬆️
5.10-m6a.metal 82.65% <100.00%> (+0.01%) ⬆️
5.10-m6g.metal 79.90% <100.00%> (+<0.01%) ⬆️
5.10-m6i.metal 83.32% <100.00%> (+0.01%) ⬆️
5.10-m7a.metal-48xl 82.64% <100.00%> (+<0.01%) ⬆️
5.10-m7g.metal 79.90% <100.00%> (+0.01%) ⬆️
5.10-m7i.metal-24xl 83.30% <100.00%> (+0.01%) ⬆️
5.10-m7i.metal-48xl 83.29% <100.00%> (+<0.01%) ⬆️
5.10-m8g.metal-24xl 79.90% <100.00%> (+0.01%) ⬆️
5.10-m8g.metal-48xl 79.90% <100.00%> (+0.01%) ⬆️
5.10-m8i.metal-48xl 83.30% <100.00%> (+<0.01%) ⬆️
5.10-m8i.metal-96xl 83.30% <100.00%> (+0.01%) ⬆️
6.1-m5n.metal 83.35% <100.00%> (+<0.01%) ⬆️
6.1-m6a.metal 82.67% <100.00%> (?)
6.1-m6g.metal 79.90% <100.00%> (+0.01%) ⬆️
6.1-m6i.metal 83.35% <100.00%> (+0.01%) ⬆️
6.1-m7a.metal-48xl 82.67% <100.00%> (+0.01%) ⬆️
6.1-m7g.metal 79.90% <100.00%> (+<0.01%) ⬆️
6.1-m7i.metal-24xl 83.36% <100.00%> (+<0.01%) ⬆️
6.1-m7i.metal-48xl 83.36% <100.00%> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 79.90% <100.00%> (+0.01%) ⬆️
6.1-m8g.metal-48xl 79.90% <100.00%> (+0.01%) ⬆️
6.1-m8i.metal-48xl 83.36% <100.00%> (+<0.01%) ⬆️
6.1-m8i.metal-96xl 83.37% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ilstam ilstam added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Awaiting review Indicates that a pull request is ready to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant