generated from erix/meta
[BUG] Reject legitimate compiler-runtime trait imports during dynamic Kernel loading #35
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/bootloader#35
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
A genuine dynamically linked Kernel image cannot load LibIPC because the loader rejects a compiler-runtime trait implementation that the linked Kernel exports. The runtime-provider policy recognizes a few mangled-name prefixes rather than the complete explicitly selected runtime provider.
Reproduction
Build Kernel #141 at
2283a3821a2bb4fd94ab7310fedd05405976dd05using Integration's real registry-backed producer at5bb91d1e59c92f83efe79774c897431bf3e13615, Handoff #11 and IPC #194. Package the generated Kernel, eight shared objects, boot store, image manifest and early manifest through Bootloader #32's authenticated fixture producer. Boot with x86-64 QEMU/OVMF and one vCPU.Expected and actual behavior
The loader should resolve explicitly declared compiler-runtime imports from the original selected Kernel runtime provider and reject unrelated Kernel symbols. Instead it stops before Kernel entry with
ERIX_BOOTLOADER:KERNEL_DYNLINK_UNRESOLVED_SYMBOL.The observed missing import is core's
boolimplementation offmt::Display. It is defined in the real Kernel dynamic symbol table, but the loader's prefix rules reject its trait-implementation spelling.Environment and identity
8d98cb73393b5d104418eae4549f2859c2d29307, console release.Evidence and prior checks
The original producers completed: eight real shared objects, genuine ET_DYN Kernel with
erix_dynlink_entry, generated manifests, signed image verification and authenticated Kernel extraction. The guest verifies the image and captures one processor before the dynamic loader error. Offline symbol inspection finds the rejected import in the Kernel provider; no symbol in this graph is globally missing.An earlier input omitted the early manifest and stopped with
KERNEL_DYNLINK_MISSING_OBJECT; adding the actual generated manifest reaches the distinct symbol-policy failure. Neither run reached Kernel entry or establishes native acceptance.Tracking
Related: #32, #34 and Kernel #142.
Implemented in Bootloader #36 and Integration #783, with the manual in Docs #101. The genuine rebuilt Kernel declares 30 runtime exports from its selected inputs; the previously rejected trait import resolves without prefix exceptions. Authenticated images now reach Kernel entry and pass the topology data diagnostic on 1, 2 and 4 vCPUs. The repair remains under review; loaded-image ownership and AP execution are separate requirements.