aboutsummaryrefslogtreecommitdiffstats
path: root/hw/ring_wrap.py (follow)
Commit message (Collapse)AuthorAge
* eighty-fifth pass: remove the harness invoke ceiling and fuzz far deeperuser2026-09-30
The previous pass showed our harness caps every boot at about a thousand invokes, which limited every fuzz in this audit, so the ceiling was worth removing. A wrapping submit is monkeypatched onto the live processor object without editing the vendor driver. The first attempt still failed at the same index, because wrapping only the byte offset is insufficient when frames fit the ring exactly and the straddle case never fires while the write pointer itself grows out of range; keeping the pointer modulo the ring capacity fixes it, and three thousand invokes now complete cleanly. That independently reconfirms the previous pass's diagnosis that the ceiling was ours. With the ceiling gone, a seeded randomized fuzz runs twenty-five hundred invokes per application with up to four simultaneous field mutations drawn from a boundary-value set, checking status, stalls, writes past the declared window and drift in a periodic fixed re-probe. Three applications and seventy-five hundred invokes produce no anomalies of any class. The objective is not met, with standing results unchanged.