[BUG] Exact-entry effects precede status reply capacity admission #13
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/fatd#13
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
FAT fixed-entry mutation and touch dispatch check status reply capacity after the operation. A too-small local reply buffer can therefore reject a response after changing media or consuming the retained entry. This is a source-confirmed reply-publication defect; no executed reproduction is claimed.
Reproduction
At
dcdd48437fba7646e20e5462c314363ade9ee784, admit a private fixed-entry mkdir or touch grant, encode its valid V1 or V2 follow-up, and call provider dispatch with an output slice shorter thanVFS_STATUS_RESPONSE_V1_SIZE. Inspect the dispatch ordering: it calls the effect before encoding the status. The new regression fixtures exercise every short output length on selected FAT12 and exFAT, then retry with a complete response buffer and inspect the created object. They are authored and unrun.Expected and actual behavior
Expected: reject insufficient response capacity before media I/O, handle changes or one-shot consumption, leaving the grant usable for a retry.
Actual source ordering: the operation may complete before the status encoder reports insufficient capacity. No runtime output, exit status or frequency is asserted.
Environment and identity
dcdd48437fba7646e20e5462c314363ade9ee784, fixed-entry dispatch insrc/dispatch.rsandsrc/dispatch/timestamped.rs.Evidence and prior checks
Source inspection identifies the effect-before-encode ordering in both mutation and touch families. The repair preflights complete status capacity before invoking either effect, preserving existing fail-stop handling. Authored controls compare output bytes, complete handle state and device event counts before retrying the unchanged request. Tests, builds, lint/format checks, VM/profiler execution and CI observation are deferred by user; none is represented as passing.
Tracking
The repair accompanies retained-entry migration, the FAT review, and Phase 6 tracking.
Source repair is signed and pushed in the FAT entry change. Authored controls cover every short status length for V1/V2 creation and touch on selected FAT12/exFAT, preserving media events and complete handle state before a successful-capacity retry. Closed as source-complete under the testing/CI waiver; no executed test, compiler or CI result is asserted.
erikinkinen referenced this issue from erix/vfsd2026-10-01 12:59:01 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 12:59:03 +02:00
erikinkinen referenced this issue from erix/vfsd2026-10-01 12:59:04 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 12:59:04 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 12:59:05 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 12:59:06 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 12:59:06 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 12:59:07 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 12:59:07 +02:00
erikinkinen referenced this issue2026-10-01 12:59:08 +02:00