Repository navigation
Conversation
GAPS.md now has a section on the boot stage contract that the self-update record depends on, and on the boot stage walking the slots after the confirm, which makes RecordSession::open() drop the session without a revert. The trial watchdog, the lock on the tried-mark region and the handover mechanism belong to the boot stage, which the tree does not hold, so the tree has no code for them. The bullet on joining the QEMU self-update scenarios into one run now also lists a board that wires RecordSession on flash and a boot stage that reads the record. Signed-off-by: Christina Quast <christina.quast@9elements.com>
chrysh
force-pushed
the
self-update-record
branch
from
November 13, 2026 16:16
874b25b to
14a2446
Compare
chrysh
force-pushed
the
self-update-gaps
branch
from
November 13, 2026 16:17
1d2e745 to
a68dab3
Compare
This was referenced Nov 13, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The self-update record in #41 depends on a boot stage that the tree does not hold. GAPS.md does not list what the boot stage starts after a lost record or a flash fault on the newest record copy.
This PR adds a GAPS.md section on the self-update record, on top of #41.
A question for reviewers. Take an update that raised the SVN. A flash fault hits the record copy that holds the
Committedsession, between the SVN floor advance andcomplete(). The boot stage then reads the older copy, which holds theTrialPendingsession. The SVN floor check rejects the confirmed image,selectreads the trial as tried and excludes the trial slot from the walk, and on a layout of 2 slots the boot stage starts the golden image in recovery mode. Is recovery mode the accepted outcome for this fault?