eve-core: enable EROFS + DM_VERITY for split-rootfs#248
Draft
eriknordmark wants to merge 1 commit into
Draft
Conversation
Add CONFIG_EROFS_FS=y, CONFIG_EROFS_FS_ZIP=y (LZ4 decompression for the lz4hc-compressed Extension image) and CONFIG_DM_VERITY=y so extsloader can veritysetup-open and mount the split-rootfs Extension. Device-mapper base (CONFIG_MD, CONFIG_BLK_DEV_DM) and CRYPTO_SHA256 were already present. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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 split-rootfs feature delivers EVE's non-critical services in a separate
Extension image — an EROFS filesystem, dm-verity protected — that
extsloaderopens withveritysetupand mounts read-only at/persist/exts.The stock
eve-core_defconfigenables neither EROFS nor dm-verity, so on astock-kernel build the Extension cannot mount; an OTA to a split image then
fails the extension-readiness check and the device rolls back to the previous
image.
This enables the three options the feature needs in
arch/x86/configs/eve-core_defconfig:CONFIG_EROFS_FSandCONFIG_EROFS_FS_ZIP— the Extension is builtlz4hc-compressed (
mkfs.erofs -zlz4hc), so the ZIP/decompression support isrequired to mount it.
CONFIG_DM_VERITY— the device-mapper base (CONFIG_MD,CONFIG_BLK_DEV_DM)and SHA-256 were already present.
Validated end-to-end on amd64/QEMU: with this kernel,
extsloaderreachesready, the verity device opens and the EROFS extension mounts, and an OTA froman old (300 MB-partition) image to the split/universal image passes the
extension-readiness gate instead of rolling back.
amd64 (
eve-core_defconfig) only; the arm64 equivalent is a follow-up.Opening as draft alongside the in-progress split-rootfs EVE work.
🤖 Generated with Claude Code