Skip to content

2026.10.16.2: a home inside a Luban system builds its catalog; the host's userland as the host has it; editions an older client can use - #677

Merged
Sunrisepeak merged 1 commit into
mainfrom
release/2026.10.16.2
Oct 16, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
release/2026.10.16.2

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Summary

Fixes the defects found after 2026.10.16.1 in the post-release verification and in main CI. Plan, evidence and the revisions made during implementation: .agents/docs/2026-10-16-post-release-defects-and-fix-plan.md. Version 2026.10.16.2.

D1: a home inside a Luban system can build its catalog. Inside a system, every home other than /xlings failed with metadata boundary: Lua worker isolation unavailable (mcpp's registry, a regular user's own home, any new home). The cause: the layer boundary requires bwrap, and the system forbids nested user namespaces.

  • The boundary exists so that a recipe does not write the layer below it or a borrowed payload, which makes it a write boundary.
  • When the boundary is required by the layer alone (no user-declared policy), the process is inside a system, bwrap cannot start and Landlock is available, the Lua worker is compiled for Landlock. It puts up the fence before it reads a request. Writable: its scratch, /dev, its hook logs, and the directory of the payload being installed. The system's own pid namespace provides pid isolation. Signal and abstract-socket scopes are added on ABI 6.
  • select() is unchanged for sessions: Landlock is still never chosen on its own.
  • On a host without bwrap the boundary is still refused.

D8: a home that declares upstreams has no system layer. Inside a system, mcpp's registry declares upstreams = /xlings and was also layered on /xlings. Payloads were then used in place with no entry in the registry's store, and mcpp reported patchelf missing. Such a home now borrows only through its upstreams, so each payload has a link entry in its own store.

D2: the sandbox shows the host's userland as the host has it. /bin, /sbin and /lib* are bound from where the host's copies resolve. On Alpine and openSUSE Leap 15, /usr/lib used to be bound over the host's own /lib or /lib64, and /bin/sh could not find its loader (host-matrix u-alpine, u-alpine-arm, u-leap-15). A host_resolve seam keeps the goldens host-independent.

D3/D4: libxpkg 0.0.64 (openxlings/libxpkg#49).

  • A platform-level ref or inherits is now inheritance, not a version named ref.
  • A version entry may state min_client. With no version named, a version this client cannot use is passed over for the newest one it can, and the client says so (luban-tiny@2026.10.16.1 needs xlings >= …; using …).

D5: installing a runtime package itself now refreshes <home>/abi.

D6: xlings-ci-luban-fresh, when triggered by a release, first waits until the published index (xim-index-pointers.json source_commit) has xlings and luban-os latest set to the release.

D7:

  • SessionWakeup is timed from the child's exit (its zombie state), so a slow start under ASan is not counted.
  • quick_install.ps1 fetches a named version's asset directly, without the GitHub or GitCode release API (which returned 403 and 429 under rate limits).

Docs:

  • 11-sandbox-and-policy: host userland, and recipes of a layered home.
  • specs/xlings-json: upstreams with no system layer.
  • luban/02-editions: min_client selection.
  • 92-release: the version files and the luban-fresh wait.
  • All with zh versions.

Test

  • Unit:
    • Confine.TheHostsProgramAndLibraryDirectoriesAreWhereTheHostsResolve (merged-usr, Alpine, Leap)
    • HomeLayers.AHomeThatDeclaresUpstreamsHasNoSystemLayer
    • XimSelectVersionMinClient.NoHintPassesOverAVersionThisClientCannotUse
    • SubosSpec legacy argv updated, INTENT-EQ golden re-recorded (summaries unchanged, 173 hashes)
    • SessionWakeup timed from the exit
  • e2e luban_image_test.sh: inside a system made by luban new, a home of its own runs xlings update behind the fence, and a recipe's top level writing /root is refused (LAYER-BOUNDARY-IN-SYSTEM).
  • Locally, inside a Luban core system on the sandbox carrier, with this build:
    • XLINGS_HOME=<new home> xlings update && xlings install succeeds.
    • A recipe's write to /root is refused, while root can write /root directly.
    • As mcpp's xlings, mcpp new && mcpp build && mcpp run uses the system's gcc (a link into /xlings) and downloads no toolchain. This needs xim-pkgindex#987 (gcc keeps a borrowed payload's specs).

Depends on openxlings/libxpkg#49 (merged) and openxlings/xim-pkgindex#987.

Co-authored-by: speak-agent 248744407+speak-agent@users.noreply.github.com

…ck write fence); the host's userland as the host has it; editions an older client can use; runtime links on a runtime's install

- Layer boundary inside a system: where bwrap cannot start (no nested user
  namespaces) and the boundary is the layer's alone, the Lua worker puts up
  a Landlock write fence before it reads a request (its scratch, /dev, its
  hook logs and the payload's directory) and the system's pid namespace
  stands for pid; scopes on ABI 6. A host without bwrap still refuses.
- A home that declares upstreams has no system layer: it borrows through
  them, so every payload it uses has an entry in its own store (mcpp's
  registry inside a system).
- Sandbox userland: /bin, /sbin and /lib* where the host's resolve (Alpine,
  openSUSE Leap 15 had /usr/lib bound over their own /lib, /lib64).
- libxpkg 0.0.64: a platform-level ref/inherits is inheritance; a version's
  min_client. With no version named, a version this client cannot use is
  passed over for the newest it can, and said so.
- A runtime installed refreshes <home>/abi.
- luban-fresh waits for the published index to carry the release.
- SessionWakeup is timed from the child's exit; quick_install.ps1 reaches a
  named version without the release API.

Plan: .agents/docs/2026-10-16-post-release-defects-and-fix-plan.md.

Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
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