Skip to content

test(root-mount): the namespace case states the mntns-owner capability; docs: the GitHub proxy fallback - #734

Merged
Sunrisepeak merged 1 commit into
mainfrom
test/root-mount-owner-capability
Nov 22, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
test/root-mount-owner-capability

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Root mount

normalize() proves a captured namespace's authority from the owner of its mount namespace (NS_GET_USERNS). A process in a user namespace nested under another process's cannot name that owner: the kernel answers EPERM. So RootMount failed on such a host while it holds on GitHub's runners.

  • The testkit probes this as the capability mntns-owner.
  • RootMount.ACapturedNamespaceRefusesABindingOutsideTheRoot requires it. The checks on invalid descriptors stay in a case of their own with no requirement.
  • The Linux unit lane declares mntns-owner, so a missing capability fails there and skips elsewhere with the reason. Measured in a nested namespace: the case skips and the invalid-descriptor case passes.
  • The refusal on EPERM states the cause.

Mirrors

mirror (GLOBAL/CN) selects where xlings' own resources come from. A recipe's GitHub URL also has third-party proxy candidates; they are latency-ordered when the recipe states the sha256 and governed by mirror_fallback (auto/off/force). The behaviour is unchanged; docs/05-indexes-and-mirrors.md now states it in English and Chinese, so a proxy that comes first under GLOBAL reads as designed.

…y; docs: the GitHub proxy fallback and mirror_fallback

normalize() proves a captured namespace's authority from the owner of its
mount namespace (NS_GET_USERNS). A process in a user namespace nested under
another process's cannot name that owner (EPERM), so the case failed there
while it holds on GitHub's runners. The testkit probes it as the capability
mntns-owner; the case requires it, and the Linux unit lane declares it, so it
fails there when missing and skips elsewhere with the reason. The refusal on
EPERM states the cause.

The mirror region selects where xlings' own resources come from; a recipe's
GitHub URL has third-party proxy candidates, latency-ordered when the sha256
is stated, governed by mirror_fallback. The indexes-and-mirrors chapter
states both, in English and Chinese.
@Sunrisepeak
Sunrisepeak merged commit a315af9 into main Nov 22, 2026
35 checks passed
@Sunrisepeak
Sunrisepeak deleted the test/root-mount-owner-capability branch November 22, 2026 10:09
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