Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Ping-Ke Shih <pkshih@realtek.com>, Kalle Valo <kvalo@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] wifi: rtw88: usb: fix memory leaks on USB write failures
Date: Thu, 07 May 2026 18:31:40 +0200	[thread overview]
Message-ID: <DBEAB6DF-B4E4-4C4A-A570-0CC0392B0406@linux.dev> (raw)
In-Reply-To: <20260507162827.69168-1-luka.gejak@linux.dev>

On May 7, 2026 6:28:27 PM GMT+02:00, luka.gejak@linux.dev wrote:
>From: Luka Gejak <luka.gejak@linux.dev>
>
>When rtw_usb_write_port() fails to submit a USB Request Block (URB)
>(e.g., due to device disconnect or ENOMEM), the completion callback is
>never executed.
>
>Currently, the driver ignores the return value of rtw_usb_write_port()
>in rtw_usb_write_data() and rtw_usb_tx_agg_skb(). Because these
>functions rely on the completion callback to free the socket buffers
>(skbs) and the transaction control block (txcb), a submission failure
>results in:
>1. A memory leak of the allocated skb in rtw_usb_write_data().
>2. A memory leak of the txcb structure and all aggregated skbs in
>   rtw_usb_tx_agg_skb().
>
>Fix this by checking the return value of rtw_usb_write_port(). If it
>fails, explicitly free the skb in rtw_usb_write_data(), and properly
>purge the tx_ack_queue and free the txcb in rtw_usb_tx_agg_skb().
>
>The issue was discovered in practice during device disconnect/reconnect
>scenarios and memory pressure conditions. Tested by verifying normal TX
>operation continues after the fix without regressions.
>
>Fixes: 87caeef032fc ("wifi: rtw88: Add rtw8723du chipset support")
>Cc: stable@vger.kernel.org
>Tested-by: Luka Gejak <luka.gejak@linux.dev>
>Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
>---
>Changes in v2:
> - Use ret = rtw_usb_write_port(...); style, and check by next line (in
>   rtw_usb_tx_agg_skb)
> - Remove unnecessary comment
> - Use ieee80211_purge_tx_queue() instead of skb_queue_purge()
> - Add testing details to commit message
>
> drivers/net/wireless/realtek/rtw88/usb.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/net/wireless/realtek/rtw88/usb.c b/drivers/net/wireless/realtek/rtw88/usb.c
>index 718940ebba31..1bb922cc2928 100644
>--- a/drivers/net/wireless/realtek/rtw88/usb.c
>+++ b/drivers/net/wireless/realtek/rtw88/usb.c
>@@ -399,6 +399,7 @@ static bool rtw_usb_tx_agg_skb(struct rtw_usb *rtwusb, struct sk_buff_head *list
> 	int agg_num = 0;
> 	unsigned int align_next = 0;
> 	u8 qsel;
>+	int ret;
> 
> 	if (skb_queue_empty(list))
> 		return false;
>@@ -456,7 +457,13 @@ static bool rtw_usb_tx_agg_skb(struct rtw_usb *rtwusb, struct sk_buff_head *list
> 	tx_desc = (struct rtw_tx_desc *)skb_head->data;
> 	qsel = le32_get_bits(tx_desc->w1, RTW_TX_DESC_W1_QSEL);
> 
>-	rtw_usb_write_port(rtwdev, qsel, skb_head, rtw_usb_write_port_tx_complete, txcb);
>+	ret = rtw_usb_write_port(rtwdev, qsel, skb_head,
>+			         rtw_usb_write_port_tx_complete, txcb);
>+	if (ret) {
>+		ieee80211_purge_tx_queue(rtwdev->hw, &txcb->tx_ack_queue);
>+		kfree(txcb);
>+		return false;
>+	}
> 
> 	return true;
> }
>@@ -518,8 +525,10 @@ static int rtw_usb_write_data(struct rtw_dev *rtwdev,
> 
> 	ret = rtw_usb_write_port(rtwdev, qsel, skb,
> 				 rtw_usb_write_port_complete, skb);
>-	if (unlikely(ret))
>+	if (unlikely(ret)) {
> 		rtw_err(rtwdev, "failed to do USB write, ret=%d\n", ret);
>+		dev_kfree_skb_any(skb);
>+	}
> 
> 	return ret;
> }

I accidentally sent this as part of the patch series but it is clearly
not. Resending as a standalone patch. Sorry for the noise.
Best regards,
Luka Gejak

      reply	other threads:[~2026-05-07 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 16:28 [PATCH v2 2/2] wifi: rtw88: usb: fix memory leaks on USB write failures luka.gejak
2026-05-07 16:31 ` Luka Gejak [this message]

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=DBEAB6DF-B4E4-4C4A-A570-0CC0392B0406@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=s.hauer@pengutronix.de \
    --cc=stable@vger.kernel.org \
    /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