From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Bo Jiao <bo.jiao@mediatek.com>
Cc: Felix Fietkau <nbd@nbd.name>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Sujuan Chen <sujuan.chen@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Evelyn Tsai <evelyn.tsai@mediatek.com>,
linux-mediatek <linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v2] wifi: mt76: fix potential memory leakage
Date: Mon, 19 Dec 2022 10:55:30 +0100 [thread overview]
Message-ID: <Y6A1Et1yzcWnWhpy@lore-desk> (raw)
In-Reply-To: <0a218783098a6b1b90ff120c7182acee93dc8feb.1671423784.git.Bo.Jiao@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 3286 bytes --]
> From: Bo Jiao <Bo.Jiao@mediatek.com>
>
> fix potential memory leakage, recycle rxwi when mt76_dma_add_buf() call fail.
>
> Signed-off-by: Bo Jiao <Bo.Jiao@mediatek.com>
> ---
> v2:
> - recycle rxwi when page_frag_alloc() and dma_map_single() fail.
> ---
> drivers/net/wireless/mediatek/mt76/dma.c | 27 ++++++++++++++----------
> 1 file changed, 16 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/wireless/mediatek/mt76/dma.c b/drivers/net/wireless/mediatek/mt76/dma.c
> index fc24b35..76ad47d 100644
> --- a/drivers/net/wireless/mediatek/mt76/dma.c
> +++ b/drivers/net/wireless/mediatek/mt76/dma.c
> @@ -580,24 +580,29 @@ mt76_dma_rx_fill(struct mt76_dev *dev, struct mt76_queue *q)
>
> buf = page_frag_alloc(&q->rx_page, q->buf_size, GFP_ATOMIC);
> if (!buf)
> - break;
> + goto out;
>
> addr = dma_map_single(dev->dma_dev, buf, len, DMA_FROM_DEVICE);
> - if (unlikely(dma_mapping_error(dev->dma_dev, addr))) {
> - skb_free_frag(buf);
> - break;
> - }
> + if (unlikely(dma_mapping_error(dev->dma_dev, addr)))
> + goto free;
>
> qbuf.addr = addr + offset;
> qbuf.len = len - offset;
> qbuf.skip_unmap = false;
> - if (mt76_dma_add_buf(dev, q, &qbuf, 1, 0, buf, t) < 0) {
> - dma_unmap_single(dev->dma_dev, addr, len,
> - DMA_FROM_DEVICE);
> - skb_free_frag(buf);
> - break;
> - }
> + if (mt76_dma_add_buf(dev, q, &qbuf, 1, 0, buf, t) < 0)
> + goto umap;
> +
> frames++;
> + continue;
> +
> +umap:
> + dma_unmap_single(dev->dma_dev, addr, len,
> + DMA_FROM_DEVICE);
> +free:
> + skb_free_frag(buf);
> +out:
> + mt76_put_rxwi(dev, t);
> + break;
> }
>
> if (frames)
Hi Bo,
I guess in the way below, the code is more readable, what do you think?
Regards,
Lorenzo
diff --git a/drivers/net/wireless/mediatek/mt76/dma.c b/drivers/net/wireless/mediatek/mt76/dma.c
index fad5fe19fe18..001538f698f1 100644
--- a/drivers/net/wireless/mediatek/mt76/dma.c
+++ b/drivers/net/wireless/mediatek/mt76/dma.c
@@ -571,13 +571,6 @@ mt76_dma_rx_fill(struct mt76_dev *dev, struct mt76_queue *q)
struct mt76_queue_buf qbuf;
void *buf = NULL;
- if ((q->flags & MT_QFLAG_WED) &&
- FIELD_GET(MT_QFLAG_WED_TYPE, q->flags) == MT76_WED_Q_RX) {
- t = mt76_get_rxwi(dev);
- if (!t)
- break;
- }
-
buf = page_frag_alloc(&q->rx_page, q->buf_size, GFP_ATOMIC);
if (!buf)
break;
@@ -588,16 +581,27 @@ mt76_dma_rx_fill(struct mt76_dev *dev, struct mt76_queue *q)
break;
}
+ if ((q->flags & MT_QFLAG_WED) &&
+ FIELD_GET(MT_QFLAG_WED_TYPE, q->flags) == MT76_WED_Q_RX) {
+ t = mt76_get_rxwi(dev);
+ if (!t)
+ goto unmap;
+ }
+
qbuf.addr = addr + offset;
qbuf.len = len - offset;
qbuf.skip_unmap = false;
- if (mt76_dma_add_buf(dev, q, &qbuf, 1, 0, buf, t) < 0) {
- dma_unmap_single(dev->dma_dev, addr, len,
- DMA_FROM_DEVICE);
- skb_free_frag(buf);
- break;
+
+ if (!mt76_dma_add_buf(dev, q, &qbuf, 1, 0, buf, t)) {
+ frames++;
+ continue;
}
- frames++;
+
+unmap:
+ dma_unmap_single(dev->dma_dev, addr, len, DMA_FROM_DEVICE);
+ skb_free_frag(buf);
+ mt76_put_rxwi(dev, t);
+ break;
}
if (frames)
> --
> 2.18.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-19 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 4:48 [PATCH v2] wifi: mt76: fix potential memory leakage Bo Jiao
2022-12-19 9:55 ` Lorenzo Bianconi [this message]
2022-12-20 4:42 ` Sujuan Chen (陈素娟)
2022-12-21 10:26 ` lorenzo
2022-12-21 14:48 ` Sujuan Chen (陈素娟)
2022-12-21 15:12 ` Felix Fietkau
2022-12-21 18:02 ` Lorenzo Bianconi
2022-12-22 8:51 ` Sujuan Chen (陈素娟)
2022-12-22 9:44 ` lorenzo
2022-12-22 14:01 ` Sujuan Chen (陈素娟)
2022-12-22 14:26 ` lorenzo
2022-12-22 23:57 ` lorenzo
2023-01-06 4:04 ` Sujuan Chen (陈素娟)
2023-01-03 1:55 ` Sujuan Chen (陈素娟)
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=Y6A1Et1yzcWnWhpy@lore-desk \
--to=lorenzo@kernel.org \
--cc=bo.jiao@mediatek.com \
--cc=evelyn.tsai@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).