mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 23:49:56 -04:00
Check that an arm keeps its region marked while a range in flight there ends, which the review found untested.
memory.c mem_lazy_arm marks the region it protects in lz_arm_r, so that lazy_flags_locked keeps lzr set when a release's flight in the same region ends during the arm's clean test. Without that mark the flight's end cleared lzr, lazy_fault let a read of the arming range go, and access_fault passed it to the crash handler. All 20 scenarios of tests/lazy_fetch_check.py passed with the mark taken out. The new arm_flight scenario has a release fetch one range for 100 ms, an arm of another range of the region wait 400 ms in its clean test, and a read of that range fault after the flight ended: it passes, and exits with an access violation when lazy_flags_locked ignores lz_arm_r. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -33,6 +33,7 @@ SCENARIOS = {
|
||||
'release': ('release', {}),
|
||||
'release_join': ('release_join', {}),
|
||||
'arm_busy': ('arm_busy', {}),
|
||||
'arm_flight': ('arm_flight', {}),
|
||||
'foreign': ('foreign', {}),
|
||||
'chunk': ('chunk', CHUNK),
|
||||
'locked': ('locked', LOCKED),
|
||||
|
||||
Reference in New Issue
Block a user