Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E8D67605A2
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] ath9k: Don't trust TX status TID number when reporting
 airtime
From:   Kalle Valo <kvalo@codeaurora.org>
In-Reply-To: <20190307183944.11190-1-toke@redhat.com>
References: <20190307183944.11190-1-toke@redhat.com>
To:     =?utf-8?q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@redhat.com>
Cc:     linux-wireless@vger.kernel.org,
        =?utf-8?q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@redhat.com>,
        Miguel Catalan Cid <miguel.catalan@i2cat.net>
User-Agent: pwcli/0.0.0-git (https://github.com/kvalo/pwcli/) Python/2.7.12
Message-Id: <20190429145236.D162E60E41@smtp.codeaurora.org>
Date:   Mon, 29 Apr 2019 14:52:36 +0000 (UTC)
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Toke Høiland-Jørgensen wrote:

> As already noted a comment in ath_tx_complete_aggr(), the hardware will
> occasionally send a TX status with the wrong tid number. If we trust the
> value, airtime usage will be reported to the wrong AC, which can cause the
> deficit on that AC to become very low, blocking subsequent attempts to
> transmit.
> 
> To fix this, account airtime usage to the TID number from the original skb,
> instead of the one in the hardware TX status report.
> 
> Reported-by: Miguel Catalan Cid <miguel.catalan@i2cat.net>
> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath-next branch of ath.git, thanks.

389b72e58259 ath9k: Don't trust TX status TID number when reporting airtime

-- 
https://patchwork.kernel.org/patch/10843731/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches