mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-16 11:49:59 -04:00
fs_host.c file_of copied the slot's host file under the shared lock and let go of the lock, and read_file, write_file, file_size, set_file_size and flush_file then used it with no lock, while close_file on another thread cleared the slot and closed the file at once. Windows hands a closed HANDLE's value to the next file opened (the audit's probe got it back in 100 of 100 rounds and read the other file through the stale value), so a call under way went on in another file: a save write could land in the wrong one. Only the game's own misuse of a handle reaches it; this is the open file half of AUDIT's F-1-09. Each call now counts itself in its slot from file_of to a new file_release. close_file closes at once when no call is under way and otherwise marks the slot closing; the last call out closes the file (file_closed, with the save bookkeeping close_file had). Nothing waits for another call, the slot and so the guest's handle value is not handed out again before the close, and a call after the CloseFile gets FS_R_INVALID_ARGUMENT, as before for a closed handle. Holding the lock across the I/O was not taken: opens and closes on every guest thread would then wait for save reads and writes, and write_file's save_touched can wait for a Commit. Reproduced before the change with stand-in host files that reuse a closed handle's value: the new tests/fs_file_use_check.py built against the old functions closed during a read, gave the next open the same handle, and the read returned the other file's bytes. With the change it passes (a close during a read happens after it, once; a call after the close is refused; 20000 close-and-open rounds beside a reading thread read no foreign bytes), as do save_share_check, save_retry_check, save_zip_check and the compile checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
102 KiB
102 KiB