Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: linux-wireless@vger.kernel.org,
	Mehmet Fide <mehmet.fide@gmail.com>,
	Ping-Ke Shih <pkshih@realtek.com>
Cc: Tzu-En Huang <tehuang@realtek.com>,
	Yan-Hsuan Chuang <yhchuang@realtek.com>,
	Kalle Valo <kvalo@kernel.org>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Brian Norris <briannorris@chromium.org>,
	linux-kernel@vger.kernel.org, mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next 2/3] wifi: rtw88: report the frames purged from the TX report queue
Date: Fri, 13 Nov 2026 07:55:37 +0100	[thread overview]
Message-ID: <89B03654-2285-4A15-A5B2-91B0F355B7E2@linux.dev> (raw)
In-Reply-To: <20261111213239.569224-3-mehmet.fide@gmail.com>

On November 11, 2026 10:32:38 PM GMT+01:00, Mehmet Fide
<mehmet.fide@gmail.com> wrote:
>From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
>A frame whose sender asked for its TX status waits in the TX report
>queue for the report of the firmware. When no report comes, the purge
>timer frees the frames with skb_queue_purge(), and rtw_core_deinit()
>does the same. mac80211 is not told: the sender gets no status, and the
>copy mac80211 keeps for the status of a frame from user space stays in
>its list until ieee80211_free_hw() warns about it. On an RTL8822CE with
>hostapd, after a firmware crash and an unbind of the driver:
>
>rtw88_8822ce 0000:01:00.0: failed to get tx report from firmware
>[...]
>Have pending ack frames!
>WARNING: net/mac80211/main.c:1761 at ieee80211_free_ack_frame+0x4c/0x70 [mac80211], CPU#1: sh/24725
>Call trace:
> ieee80211_free_ack_frame+0x4c/0x70 [mac80211] (P)
> idr_for_each+0x6c/0xf4
> ieee80211_free_hw+0x30/0x8c [mac80211]
> rtw_pci_remove+0xd8/0xf0 [rtw88_pci]
> pci_device_remove+0x44/0xd4
>
>Take the frames off the queue under its lock and hand them to
>ieee80211_purge_tx_queue(), which reports each one as not sent.
>
>Fixes: e3037485c68e ("rtw88: new Realtek 802.11ac driver")
>Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
>---

Looks good to me,

Reviewed-by: Luka Gejak <luka.gejak@linux.dev>

Best regards,
Luka Gejak

  reply	other threads:[~2026-11-13  6:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 21:32 [PATCH rtw-next 0/3] wifi: rtw88: three fixes around the firmware recovery Mehmet Fide
2026-11-11 21:32 ` [PATCH rtw-next 1/3] wifi: rtw88: free the reserved pages of an interface on " Mehmet Fide
2026-11-13  6:54   ` Luka Gejak
2026-11-11 21:32 ` [PATCH rtw-next 2/3] wifi: rtw88: report the frames purged from the TX report queue Mehmet Fide
2026-11-13  6:55   ` Luka Gejak [this message]
2026-11-11 21:32 ` [PATCH rtw-next 3/3] wifi: rtw88: reset the stations outside of RCU on firmware recovery Mehmet Fide
2026-11-13  6:57   ` Luka Gejak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89B03654-2285-4A15-A5B2-91B0F355B7E2@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=briannorris@chromium.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mehmet.fide@gmail.com \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=pkshih@realtek.com \
    --cc=sgruszka@redhat.com \
    --cc=tehuang@realtek.com \
    --cc=yhchuang@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox