ieee80211: use response rate for fragmented-frame ACK duration - #1200
Open
mgonzalezlopezudc wants to merge 1 commit into
Open
mgonzalezlopezudc wants to merge 1 commit into
mgonzalezlopezudc wants to merge 1 commit into
Conversation
Reserve the ACK following the next DCF fragment using its response mode. A production exchange at 54 Mbps with 24 Mbps ACKs now reserves the missing four microseconds. The focused module test and all four fragmentation fingerprints pass. Change: src.ieee80211.duration | behavior.change.fix | test | wifi-audit
mgonzalezlopezudc
marked this pull request as ready for review
September 15, 2026 23:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
A fragmented DCF frame reserved its next ACK at the data rate. Select the next fragment’s response ACK mode; the 54/24-Mbps case now reserves the additional four microseconds.
Scope
Originator protection mechanism; no configuration change.
Dependencies and merge order
No prerequisite within this audit series; this topic was built and tested independently on the pinned base.
Validation
Pinned test base:
7287f347aaca36e557c708d6930a6f5a450b2833.The isolated topic head passed an assertions-enabled debug build (
-O0 -Wall -g0; debug symbols omitted for storage) and the focused checks below. The larger integration source tree also passed debug and release compilation; no separate release build is claimed for this topic.Executed focused test commands, from the repository root after
source setenv -q:inet_run_module_tests -m debug -f 'Ieee80211FragmentAckDuration_1\.test'Results: 1 module cases passed.
Limits and review status
Independent of fractional Duration rounding.
Draft pending final independent review and reconciliation with current upstream. Live PR overlap has not been reverified against the pinned test base.