Repository navigation
P105: integrate SwissPPNFTL reclamation into normal writes - #93
shaynelegault wants to merge 8 commits into
Conversation
e1c4d55 to
9e0fd8e
Compare
Add the append writes of #91 to kernel/patches/armv7/mtd: the iOS disk of the 64 GB iPad mini 1 becomes writable. Writing is part of the driver; the default-off MTD_APPLE_SFTL_WRITE option and the write_enable module parameter are gone. The disk stays read-only only when the replayed journal does not end at the allocation floor. Without reclamation (#93), writes fail once the blank blocks are used up. The patch keeps Shayne Legault as author and notes the changes and his original commit IDs. The bring-up notes and the board README follow the driver as carried. Assisted-by: LLM
Add the append writes of OrchardLinux#91 to kernel/patches/armv7/mtd: the iOS disk of the 64 GB iPad mini 1 becomes writable. Writing is part of the driver; the default-off MTD_APPLE_SFTL_WRITE option and the write_enable module parameter are gone. The disk stays read-only only when the replayed journal does not end at the allocation floor. Without reclamation (OrchardLinux#93), writes fail once the blank blocks are used up. The patch keeps Shayne Legault as author and notes the changes and his original commit IDs. The bring-up notes and the board README follow the driver as carried. Assisted-by: LLM
|
Thanks, Shayne. Marking this as a draft until reclamation is finished: we'll merge it once the erase and GC side that uses this planner is in place and it runs end to end. When you get there, 32-bit kernel patches now live in kernel/patches/armv7/mtd/ (listed in kernel/series/apple-armv7), without .patch.toml scope files. |
Export the offline SwissPPNFTL checkpoint and reclamation work from the merged ARMv7 append writer. Carry the kernel changes in the ARMv7 MTD series and document the current append-only behavior and remaining runtime work. Assisted-by: LLM
9e0fd8e to
3aff97d
Compare
Export the verified H2FMI erase operation, live page copier and SFTL allocator from the ARMv7 kernel at ccd56d3c440c. Record the synthetic end-to-end tests and the native checkpoint and hardware qualification still required for P105. Assisted-by: LLM
Export the native-format save and recovery path, healthy VFL rotation and block-accounting guards to the ARMv7 MTD series. Record the captured-media and interruption results, and the provider accounting still needed before enabling physical erase and reuse. Assisted-by: LLM
Export the native provider counters, free-block and wear transitions, fresh context allocation and checkpoint publication order. Record the firmware replay, the integrity checks for unlisted context sites and the remaining physical qualification requirements for erase and reuse. Assisted-by: LLM
Serialize raw programs against the lifetime of the recovered SFTL map. Stage a board-specific module to capture both physical views and controller status, and compare paired observations along with adjacent and same-index controls. Publish matching PR kernel and measurement module artifacts for device tests. Keep physical erase disabled pending measured coverage, continuous runtime accounting and cold-boot preservation. Assisted-by: LLM
Use the checkout SHA provided by the pull request job when packaging the P105 kernel and its capture module. The runner and the build container use different owners for the worktree. Assisted-by: LLM
Stage the ARMv7 measurement build in the kernel directory layout consumed by the RAM project. Include the linked kernel notes digest so a running build can be identified independently of the release string. Let hardware-check start on kernels without the optional hotplug sysctl. Fence the P105 SFTL disk and partitions as they register and verify their mount and read-only state around the bounded storage probe. Assisted-by: LLM
|
@shaynelegault, a heads-up so nothing collides with your work here. Project Cascadia now has its own P105 NAND writer (rzxvx's The proposal keeps your structure (H2FMI provider, apple-sftl, LwVM parser, then this PR) as the base. On top of it we'd port, as separate commits credited to rzxvx:
That work goes on You're welcome to review it, take any of it over, or tell us to hold off on a part you're already doing. |
The P105's translation layer registered only on the 64 GB NAND package. Port Cascadia's 16 GB layout into it (patch 0018, authored by rzxvx): four banks of 1064 blocks of 256 pages, 1055 superblocks, the VFL in blocks 1062/1063, iOS 8.4.1's context and summary rules. A 16 GB P105 now gets a read-only applesftl disk of 16,000,000,000 bytes. 0017 first moves #93's fixed 64 GB constants into a geometry descriptor, unchanged in behaviour for the 64 GB package. KUnit gains a synthetic 16 GB medium (3 cases); all 84 apple-sftl and apple-h2fmi cases pass. Untested on hardware. Assisted-by: LLM
Capture the native iOS counters over paired USB and reject mismatched flash geometry. Document the verified raw-write exclusion and the iOS pages read through both operating systems. Keep reclamation pending its physical qualification. Assisted-by: LLM
This draft adds garbage collection to the normal write path of the 64 GB P105 SwissPPNFTL driver. The writer copies live data, publishes a native-format checkpoint, recovers the map and verifies the retired blocks before reuse. The full transaction runs on synthetic NAND. Physical P105 writes still append into verified blank blocks, and the installer retains its space warning.
Changes
reclaims = false.Verification
Kernel source · P105 bring-up evidence · GitHub Actions
Remaining before merge
Physical qualification still needs trustworthy runtime controller accounting, exclusive ownership and a measured erase footprint in normal and SLC modes. Cold-boot reuse and preservation of existing iOS data remain to be demonstrated on the P105. Scrub and bad-member replacement also remain unqualified.