Verify installed runtime-image source mappings on native hardware #147
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/kernel#147
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?
Problem and motivation
A source-backed supervisor constructor needs native evidence that the installed hardware root contains only its actual retained image, controller and table sources. Topology IDs and successful compilation do not establish alias confinement or processor permission enforcement.
Proposed behavior and scope
Add a read-only audit of the actual installed Kernel root while its original CPU, root pin, table storage, runtime/controller loans and bootstrap stack remain retained. Enumerate all owned installed entries and compare exact effective leaves, permissions and cache selectors against the allowed source plan. Account explicitly for the owned recursive table view, require it to be non-executable, and reject extra low aliases and mappings of allocation holes.
Add separate native image cases for successful source audit, a read through the withdrawn original loader-stack alias, a write to a genuine read-only runtime page, and execution through the recursive table alias. Preserve the existing architectural page-fault handler and its original hardware frame. Expected-fatal cases must verify actual fault address, instruction, supervisor mode and error bits; a missing marker or unexpected return cannot pass.
Authority, security and reliability
Actual retained root/table/stack and original allocation objects supply custody. Page-table words, addresses and diagnostic reports are observations only. The audit does not create mappings, import a memory owner or install an exception handler. It keeps local execution and table-borrow guards through readback and intentional probes. Failure retains backing and stops the diagnostic image.
Acceptance criteria
Alternatives and tradeoffs
A copied-table fixture or topology count cannot establish actual hardware mapping policy. Replacing the exception handler with a diagnostic success path would hide the original fault behavior. Read-only source-bound enumeration plus independent terminal cases tests the actual installed hierarchy without granting broader authority.
Tracking and rollout
Build on original runtime-image sources #146 and design #143. Coordinate Bootloader #34, LibHandoff #13, the source-lifetime manual and native activation #123.