Skip to content

fix: remove dead nsenter branch and update stale comments/docs#542

Closed
claude-claude[bot] wants to merge 1 commit intofix-remaining-flakyfrom
claude/fix-22568083496
Closed

fix: remove dead nsenter branch and update stale comments/docs#542
claude-claude[bot] wants to merge 1 commit intofix-remaining-flakyfrom
claude/fix-22568083496

Conversation

@claude-claude
Copy link
Copy Markdown
Contributor

@claude-claude claude-claude bot commented Mar 2, 2026

Auto-Fix for PR #541

Issues Fixed

  • Dead code: Removed unreachable nsenter branch in VmManager::start() — after PR fix: pdeathsig, namespace timeout, arping for remaining flaky tests #541 switched rootless baselines to pre_exec setns, user_namespace_path is always set when holder_pid is set, making the else if let Some(holder_pid) branch unreachable
  • Stale struct field comments: Updated holder_pid, user_namespace_path, net_namespace_path comments to reflect current usage (all rootless VMs, not just clones)
  • Stale doc comments: Updated set_holder_pid(), set_user_namespace_path(), set_net_namespace_path() docs to accurately describe the pdeathsig motivation and that these are used for all rootless VMs
  • Stale DESIGN.md: Updated step 5 from "Run Firecracker via nsenter" to "Run Firecracker via pre_exec setns"

Changes

  • src/firecracker/vm.rs: Remove dead nsenter branch (~25 lines), update all related comments and doc comments
  • DESIGN.md: Update rootless setup sequence step 5

Generated by Claude | Review Run

After PR #541 switched rootless baselines to use pre_exec setns,
the nsenter code path in VmManager::start() became unreachable
(user_namespace_path is always set when holder_pid is set). Remove
the dead branch and update all stale comments and DESIGN.md to
reflect that ALL rootless VMs now use pre_exec setns.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@ejc3
Copy link
Copy Markdown
Owner

ejc3 commented Mar 2, 2026

Fixed in #541

@ejc3 ejc3 closed this Mar 2, 2026
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.

1 participant