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.
feat(apu): implement the SMP wait states; E3.09 measures them #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
feat(apu): implement the SMP wait states; E3.09 measures them #313
Changes from all commits
0ce5aea948063e52c5498File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win
Out-of-range
$F0wait selector from a save state panics on indexing.wait_indexcastsself.internal_wait/self.external_waitdirectly tousizeandwait_clocksindexesSMP_CYCLE_WAIT/SMP_TIMER_WAIT(4-element arrays) with that index. The live write path always masks these fields with& 0x03, so normal execution never produces an out-of-range value.Io::load_statedoes not: it assignsself.external_wait = s.read_u8()?;andself.internal_wait = s.read_u8()?;directly, with no bounds check.A save-state file with either byte set above 3 makes
wait_indexreturn an index of up to 255. The first subsequent APU access callswait_clocks, which indexesSMP_CYCLE_WAIT[idx]/SMP_TIMER_WAIT[idx]and panics.Before this PR these fields were parsed but never consulted, so the missing validation in
Io::load_statewas harmless. This PR'swait_index/wait_clocksare the first code to read them as array indices, turning that gap into a crash on untrusted save-state input.Add the bounds check in
Io::load_state, consistent with howApu::load_statealready rejects an out-of-rangebase_clocks(lines 703-706) with a typed error instead of a panic.The coding guideline states: "Do not introduce
.unwrap(),.expect(), orpanic!()on untrusted external input—such as ROM/save-state bytes... Use typed errors at those boundaries."🛡️ Proposed fix in `Io::load_state` (outside the selected range, around line 334)
🤖 Prompt for AI Agents
Source: Coding guidelines
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.