Repository navigation
omamobile-fingerprint 0.1.10: map Trusty's tamper-detect stores as block devices - #101
Conversation
…ock devices Stock storageproxyd maps Trusty's TD and TDP stores to trusty_userdata and trusty_persist and takes its size limit from the TD block device. On the 9a without that mapping every TA write failed with "transaction would leave fs too full". When $STATE/td.img or tdp.img exists, the runner now loop-mounts it into the chroot, passes -f and -m as stock does, and creates the store links first, since without them storageproxyd answers "pending symlink" and Trusty sees an empty store. Without the images nothing changes. Tested on the palmtop: secure storage ready with both stores mapped.
…or the HAL The runner gave every phone the Pixel 7 Pro's panel name. The 9a's is google-tg4c, the bootloader's name for its panel, which is what Google's driver reports; OMAMOBILE_FP_PANEL_NAME overrides it. The HAL also reads the panel's id from the backlight's device (serial_number): when the panel driver exposes one, the runner now passes it into the chroot.
|
Added a second commit: the 9a's panel name (google-tg4c instead of the Pixel 7 Pro's, overridable with OMAMOBILE_FP_PANEL_NAME) and the panel id passed through as serial_number when the panel driver exposes it. The HAL reads that id, and it looks like the key for the 9a's factory calibration. This commit hasn't run on the palmtop yet (it's waiting for a hand restart); I'll post the result before you merge. |
…atomically The watchdog's jump test changes a control from a background job while the watchdog reads the fake mixer's state file, and CI once caught the read halfway through the write (JSONDecodeError, the test failed). Both fakes now write a temporary file and rename it over the state.
…aps only with their images The runner's static checks now cover what this pull request added: each phone has its own panel name and the override exists, and storageproxyd maps TD and TDP only when their images are there.
The flake had a second writer: JsonCtl, the json: control backend the tests run the speaker code against, rewrites the fake mixer's state on every heartbeat read, in place. The fake mixer reading at that moment saw an empty file. JsonCtl now writes a temporary file and renames it, as the fakes do. Nothing changes on the palmtop: JsonCtl is used only with OMAMOBILE_CTL_BACKEND=json:.
…s first reading The jump tests changed the estimate 0.4 s after starting the watchdog. On a slow CI runner the watchdog wasn't reading yet, took the raised value as its baseline, saw no jump and didn't mute. The jump now waits for the watchdog's start line and a few intervals, and the watchdog runs 60 iterations.
|
Thanks, @W4HO-ham. Mapping the stores as block devices so storageproxyd gets its Before it merges, I need three things:
The panel-name part of that commit is fine: the 7 Pro gets the same |
…er a store, and record F4 and D1 Review of the store mapping: it now runs only on the 9a (MAP_STORES in the tegu case), so a Pixel 7 Pro state directory can never take this path, and a store already at ss/0 or persist-ss/0 is moved aside with a timestamp instead of being removed by a forced link. FINGERPRINT-PLAN records D1 = A with the stores as block devices (the owner's call on 2026-10-27), F3 and F4 with their results, and a step for making td.img and tdp.img. The panel id passthrough is dropped from this pull request until a kernel change provides serial_number.
|
Thanks, all three handled in 27c2aac.
I'll post the storage stage's run of this head from the palmtop here next. |
|
Run of this head (27c2aac's runner) on the palmtop, |
|
Thanks, @W4HO-ham, this is what I hoped for. D1 and F4 are on record with the backup check and the release, and F4b says what the images are and that they never leave the phone. Two lines in the plan before it merges, and a small third:
|
…a named exception
|
All three are in FINGERPRINT-PLAN:
|
|
Thanks, @W4HO-ham. All three points from my last comment are in 932ff8f:
The newest commit only touches the plan, so the runner you ran on the palmtop at 16:04 is the runner at this head. I checked these again:
One small question, which doesn't hold up the merge: the 10-27 "night, later" entry says the live runner's I'll squash-merge this as "omamobile-fingerprint 0.1.10: map Trusty's tamper-detect stores as block devices". In the squash body I'll mention the 9a's panel name and leave out the audio commits and the panel-id commit you dropped. Thanks for the careful work and the quick turnarounds. |
L-279 to L-293: the 9a's slot B hold and what made devinfo writable (#125), per-device flags checked by building both command lines (#101), env defaults in the shared build library and CI waiting for approval (#79), GLib retry paths and radio stops checked at the controller (#99), silent re-pushes and stacks with several tops (the tegu stack), and two of our own: merge only after every check has finished (#126), and an empty diff is checked for empty inputs (kernel #123). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…wenty-sixth rounds (#127) * docs/review: 19 lessons and 3 corrections from the twenty-fifth round The confirmed candidates from round 25 (L-260 to L-278): the 9a slot B marking as a devinfo question, cross-repository links, squash-merged stacks and version files, stale hand-built prebuilts, and before-merge Pixel 7 Pro runs on omamobile-int. C-16 to C-18 correct our own earlier comments on kernel #98, kernel #80 and #74; L-241 is corrected in place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs/review: 15 lessons from the twenty-sixth round L-279 to L-293: the 9a's slot B hold and what made devinfo writable (#125), per-device flags checked by building both command lines (#101), env defaults in the shared build library and CI waiting for approval (#79), GLib retry paths and radio stops checked at the controller (#99), silent re-pushes and stacks with several tops (the tegu stack), and two of our own: merge only after every check has finished (#126), and an empty diff is checked for empty inputs (kernel #123). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for merging. To your question: right now the palmtop runs the F4b setup, |
The matrix after the merges since #118, with each cell going by the merged notes: - Pixel 7 (panther): the board file (derekross/linux-omarchy-mobile#108) and the FT3658 touch driver (derekross/linux-omarchy-mobile#109) have merged into the published kernel, so Boot, Storage, Buttons and USB net say "in the published kernel" instead of "in review". Touch stays "no": the driver and the touch rails are published, but the board file has no touch node, and panther's notes end at boot 8 with the controller not answering. BRINGUP-M1's status and NOTES' header say the same. - Pixel 6 Pro (raven), Charging: no -> works. device-raven 0.1.26 (#112, #126) loads the MAX77759 charger at boot with its temperature guard; USB-PLAN section 4 records C0-C5 passed on 2026-10-28, a full charge to 100 % included. The battery node is derekross/linux-omarchy-mobile#112; the runs were on an unpublished integration kernel, and the cell says so. - raven, Torch: still works; the LED's node is now in the published kernel (derekross/linux-omarchy-mobile#113), tested on omamobile-gs101-torch and not yet run from the published kernel. - Pixel 9a (tegu), Fingerprint: no -> WIP. FINGERPRINT-PLAN records F0 and F2-F6b passed on an unpublished kernel: Trusty's TA runs and the HAL sees the sensor; enrollment waits for the factory calibration (F6c). omamobile-fingerprint 0.1.10 (#101) maps Trusty's stores for it. Left as they were: tegu's Charging (the MAX77779 charger driver, derekross/linux-omarchy-mobile#92, is published, but tegu's notes record no run of it), the gs201 HSI2 pin controller (derekross/linux-omarchy-mobile#123, no cell), felix (#35 is a plan) and cheetah (nothing merged for it). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Stock storageproxyd maps Trusty's TD and TDP stores to
trusty_userdataandtrusty_persist, and takes its size limit (-m) from the TD block device. On the palmtop without that mapping every TA write failed with "transaction would leave fs too full".When
$STATE/td.imgor$STATE/tdp.imgexists, the runner now loop-mounts it into the chroot as/dev/block/ss-tdorss-tdp, passes-f 0:… -m …and-f persist/0:…as stock does, and creates the store links (ss/0,persist/0) before storageproxyd starts. Without them storageproxyd answers "pending symlink" and Trusty reads the store as empty. With no images nothing changes, so cheetah is unaffected.Tested on the palmtop:
omamobile-fp-chroot start storagereports secure storage ready with both stores mapped (128 MiB max file size from the TD device).tools/pr-checkandtest/allpass.Enrollment still waits on the 9a's factory calibration (FINGERPRINT-PLAN F6c); this is the storage half.